CVE-2025-65637
Public on
Last Modified:
Description
A denial-of-service vulnerability in github.com/sirupsen/logrus occurs when Entry.Writer() processes a single-line payload larger than 64KB with no newline characters. Due to a limitation in Go’s internal bufio.Scanner, the read operation fails with a “token too long” error, causing the underlying writer pipe to close. In affected versions, this leaves the Writer interface unusable and can disrupt logging functionality, potentially degrading application availability.
Statement
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 attacker-controlled input, which raises the attack complexity and reduces realistic exploitability. Additionally, the flaw does not affect confidentiality or integrity, nor does it allow code execution or privilege escalation. The failure results in a controlled degradation of availability (logging becoming non-functional), rather than a broader application outage or systemic compromise. These constrained conditions and limited real-world impact justify treating the issue as moderate rather than important.
Mitigation
Mitigation is either unavailable or does not meet Red Hat Product Security standards for usability, deployment, applicability, or stability.
Additional information
- This content is not included.Bugzilla 2418900: github.com/sirupsen/logrus: github.com/sirupsen/logrus: Denial-of-Service due to large single-line payload
- Content from cwe.mitre.org is not included.CWE-400: Uncontrolled Resource Consumption
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2025-65637
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2025-65637
Content from github.com is not included.https://github.com/mjuanxd/logrus-dos-poc
Content from github.com is not included.https://github.com/sirupsen/logrus/issues/1370
Content from github.com is not included.https://github.com/sirupsen/logrus/pull/1376
Content from github.com is not included.https://github.com/sirupsen/logrus/releases/tag/v1.8.3
Content from github.com is not included.https://github.com/sirupsen/logrus/releases/tag/v1.9.1
Content from github.com is not included.https://github.com/sirupsen/logrus/releases/tag/v1.9.3
Affected Packages and Issued Red Hat Security Errata
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | container-tools:rhel8 | Fixed | RHSA-2026:3428 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | container-tools:rhel8 | Fixed | RHSA-2026:10703 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | osbuild-composer | Fixed | RHSA-2026:2687 |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | container-tools:rhel8 | Fixed | RHSA-2026:10703 |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | osbuild-composer | Fixed | RHSA-2026:2687 |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | container-tools:rhel8 | Fixed | RHSA-2026:10703 |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | osbuild-composer | Fixed | RHSA-2026:2687 |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | osbuild-composer | Fixed | RHSA-2026:2685 |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | container-tools:rhel8 | Fixed | RHSA-2026:4693 |
| Red Hat Enterprise Linux 8.8 Telecommunications Update Service | container-tools:rhel8 | Fixed | RHSA-2026:6191 |
| No matching records found | |||
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| CVSS v3 Base Score | 7.5 | N/A | 7.5 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality Impact | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
My product is listed as "Out of Support Scope". What does this mean?
Not sure what something means? Check out our Security Glossary.