Is github.com/sirupsen/logrus 1.8 vulnerable?

Go · 4 releases from 1.8.0 to 1.8.3 · latest github.com/sirupsen/logrus is 1.10.2 · checked 18 Nov 2026

No known advisories in the last release

github.com/sirupsen/logrus 1.8.3, the last 1.8 release, has no known advisories. 2 advisories affect earlier 1.8.x releases, so update to 1.8.3.

Update within 1.8: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

Fixed within 1.8.x, affecting earlier releases

  • 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.8.x release

Affected: 1.8.0 to 1.8.2. 1.8.3 is not affected. Latest github.com/sirupsen/logrus: 1.10.2.

VersionKnown advisories
github.com/sirupsen/logrus 1.8.3None
github.com/sirupsen/logrus 1.8.2CVE-2025-65637, CVE-2025-65637
github.com/sirupsen/logrus 1.8.1CVE-2025-65637, CVE-2025-65637
github.com/sirupsen/logrus 1.8.0CVE-2025-65637, CVE-2025-65637

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

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.