How severe is GHSA-4f99-4q7p-p3gh?

No CVSS score has been assigned to GHSA-4f99-4q7p-p3gh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4f99-4q7p-p3gh?

GHSA-4f99-4q7p-p3gh affects the following packages: github.com/sirupsen/logrus (Go), github.com/sirupsen/logrus (Go), github.com/sirupsen/logrus (Go). Ecosystems affected: Go.

How do I fix GHSA-4f99-4q7p-p3gh?

Update github.com/sirupsen/logrus to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4f99-4q7p-p3gh is resolved across your whole dependency graph.

How do I detect GHSA-4f99-4q7p-p3gh in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/sirupsen/logrus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4f99-4q7p-p3gh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4f99-4q7p-p3gh?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4f99-4q7p-p3gh can be triaged on real exposure rather than presence alone.

Is GHSA-4f99-4q7p-p3gh actively exploited in the wild?

No public exploit code has been indexed for GHSA-4f99-4q7p-p3gh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4f99-4q7p-p3gh?

GHSA-4f99-4q7p-p3gh has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4f99-4q7p-p3gh?

GHSA-4f99-4q7p-p3gh is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4f99-4q7p-p3gh published, and has it been updated?

GHSA-4f99-4q7p-p3gh was published on December 4, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-4f99-4q7p-p3gh — logrus

Fix: sirupsen/logrus#1376

GHSA-4f99-4q7p-p3gh is a Uncontrolled Resource Consumption vulnerability in github.com/sirupsen/logrus. A fix is available for github.com/sirupsen/logrus — see the affected versions and patch details below.

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

Also known asCVE-2025-65637GO-2025-4188

Published

Dec 4, 2025

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4f99-4q7p-p3gh.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

🐹github.com/sirupsen/logrus🐹github.com/sirupsen/logrus🐹github.com/sirupsen/logrus

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A denial-of-service vulnerability exists in github.com/sirupsen/logrus when using Entry.Writer() to log a single-line payload larger than 64KB without newline characters. Due to limitations in the internal bufio.Scanner, the read fails with "token too long" and the writer pipe is closed, leaving Writer() unusable and causing application unavailability (DoS). This affects versions < 1.8.3, 1.9.0, and 1.9.2. The issue is fixed in 1.8.3, 1.9.1, and 1.9.3+, where the input is chunked and the writer continues to function even if an error is logged.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/sirupsen/logrus`	all versions	1.8.3`go get github.com/sirupsen/logrus@v1.8.3`
🐹Go	`github.com/sirupsen/logrus`	≥ 1.9.0&&< 1.9.1	1.9.1`go get github.com/sirupsen/logrus@v1.9.1`
🐹Go	`github.com/sirupsen/logrus`	≥ 1.9.2&&< 1.9.3	1.9.3`go get github.com/sirupsen/logrus@v1.9.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/sirupsen/logrus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/sirupsen/logrus to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4f99-4q7p-p3gh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4f99-4q7p-p3gh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4f99-4q7p-p3gh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is categorized as Moderate because its impact is limited to the logging subsystem and requires a specific, non-default usage pattern to trigger—namely, sending a single unbounded line exceeding 64KB through Entry.Writer(). Most Logrus deployments do not expose this interface directly to…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`container-tools:rhel8-8100020260204142227.afee755d`	RHSA-2026:3428
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support	`container-tools:rhel8-8060020260422144418.ad008a3a`	RHSA-2026:10703
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support	`osbuild-composer-0:46.3-5.el8_6`	RHSA-2026:2687
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	`osbuild-composer-0:75-6.el8_8`	RHSA-2026:2685
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	`container-tools:rhel8-8080020260226135022.63b34585`	RHSA-2026:4693
Red Hat Enterprise Linux 8.8 Telecommunications Update Service	`container-tools:rhel8-8080020260325222945.63b34585`	RHSA-2026:6191
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions	`oci-seccomp-bpf-hook-0:1.2.10-1.el9_0`	RHSA-2026:15940
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions	`skopeo-2:1.8.0-4.1.el9_0.3`	RHSA-2026:15941

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-4f99-4q7p-p3gh in your dependencies?

O3 Security finds GHSA-4f99-4q7p-p3gh across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works