Loading vulnerability…
CVE-2025-65637 is a denial-of-service vulnerability in github.com/sirupsen/logrus. In affected versions, Entry.Writer() processes input through Go's bufio.Scanner. A single line exceeding 64 KB with no newline delimiter exceeds the scanner token limit, causing a "token too long" read error. The resulting error closes the underlying writer pipe, after which the Writer interface remains unusable. Fixed releases chunk the input and preserve writer operation even when a logging error occurs.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) for CVE-2025-65637, a denial-of-service (DoS) vulnerability in the Go logging library github.com/sirupsen/logrus. The vulnerability is present in versions <1.8.3, 1.9.0, and 1.9.2, and is triggered when a single-line payload larger than 64KB (without newlines) is written to logrus.Writer(). This causes the internal bufio.Scanner to fail, breaking the Writer() pipe and rendering the logger unusable, which can result in application unavailability. The repository contains two Go PoC files: 'poc_logrus_dos.go' (a simple demonstration) and 'poc_logrus_dos_improved.go' (a more detailed version that checks for both the error and the DoS condition). There are also test scripts in PowerShell and Bash ('test_single_version.ps1', 'test_versions.ps1', 'test_versions.sh') to automate testing across multiple logrus versions. The README provides detailed instructions, affected/fixed version lists, and references to the CVE and upstream issue. The exploit does not target a network service directly but requires the attacker to be able to inject large payloads into logrus.Writer(), which could happen if user-controlled data is piped into the logger (e.g., via HTTP headers or subprocess output). The main attack vector is local resource exhaustion via application misuse. No external network endpoints or IPs are hardcoded in the code. The repository is well-structured for testing and demonstrating the vulnerability, and is intended for research and validation of the DoS issue in logrus.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
23 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A denial-of-service vulnerability in github.com/sirupsen/logrus caused by Entry.Writer() handling of single-line payloads larger than 64KB without newline characters, which can break logging and cause application unavailability.
A denial-of-service vulnerability in github.com/sirupsen/logrus triggered by a large single-line payload.
A denial-of-service vulnerability in github.com/sirupsen/logrus triggered by a large single-line payload.
A denial-of-service vulnerability in github.com/sirupsen/logrus triggered by a large single-line payload.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.