CVE-2025-65637

Exp

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.

Published: 2025-12-04 Last update: 2025-12-23 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-65637 is rated High Exploit Risk (60.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.56%). Core evidence: 4 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-65637

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-65637

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.56% +0.51%
2 2026-05-14 0.01% 0.06% +0.05%
3 2025-12-05 0.01%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-65637

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-65637

GitHub Security Advisory for CVE-2025-65637

GHSA-4f99-4q7p-p3gh · Severity: high · Ecosystem: go — Logrus is vulnerable to DoS when using Entry.Writer()

OS Trackers for CVE-2025-65637

vendor priority summary link
debian not yet assigned CVE-2025-65637 not yet assigned priority: Debian including 1 source packages (golang-logrus), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-65637
redhat medium https://access.redhat.com/security/cve/CVE-2025-65637
ubuntu medium CVE-2025-65637 medium priority: Ubuntu including 1 source packages (golang-logrus), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): needs-triage 6, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-65637

Affected software / configurations for CVE-2025-65637

Vendor Product Version Raw CPE
turbopuffer logrus < 1.8.3 cpe:2.3:a:turbopuffer:logrus:*:*:*:*:*:go:*:*
turbopuffer logrus 1.9.0 cpe:2.3:a:turbopuffer:logrus:1.9.0:*:*:*:*:go:*:*
turbopuffer logrus 1.9.2 cpe:2.3:a:turbopuffer:logrus:1.9.2:*:*:*:*:go:*:*

References for CVE-2025-65637

cvelogic Threat Intelligence