Is github.com/sirupsen/logrus 1.7 vulnerable?

Go · 2 releases from 1.7.0 to 1.7.1 · latest github.com/sirupsen/logrus is 1.10.2 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. github.com/sirupsen/logrus 1.7.1, the last 1.7 release, is affected by 2 known security advisories (1 high, 1 low), including CVE-2025-65637, CVE-2025-65637. Upgrade to 1.8.3 or later to fix all of them.

Upgrade with:go get github.com/sirupsen/logrus@v1.8.3

Is your project on an affected github.com/sirupsen/logrus?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting github.com/sirupsen/logrus 1.7.1

  • LowCVE-2025-65637GO-2025-418815 Dec 2025

    Logrus is vulnerable to DoS when using Entry.writerScanner in github.com/sirupsen/logrus

    Affected
    <1.8.3 · >=1.9.0 <1.9.1 · >=1.9.2 <1.9.3
    Fixed in
    1.8.3, 1.9.1, 1.9.3
  • HighCVE-2025-65637GHSA-4f99-4q7p-p3gh4 Dec 2025

    Logrus is vulnerable to DoS when using Entry.Writer()

    Affected
    <1.8.3 · >=1.9.0 <1.9.1 · >=1.9.2 <1.9.3
    Fixed in
    1.8.3, 1.9.1, 1.9.3

Every github.com/sirupsen/logrus 1.7.x release

Affected: 1.7.0 to 1.7.1. Latest github.com/sirupsen/logrus: 1.10.2.

VersionKnown advisories
github.com/sirupsen/logrus 1.7.1CVE-2025-65637, CVE-2025-65637
github.com/sirupsen/logrus 1.7.0CVE-2025-65637, CVE-2025-65637

Which of your client projects are still on github.com/sirupsen/logrus 1.7?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/sirupsen/logrus version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other github.com/sirupsen/logrus versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.