Loading vulnerability…
BinUtils 2.26 contains a denial-of-service vulnerability in the d_abi_tags function in cp-demangle.c. Processing a crafted PE file can trigger the flaw and disrupt availability.
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 is a small standalone proof-of-concept for CVE-2025-66866, targeting a denial-of-service issue in GNU Binutils demangling logic, specifically the d_abi_tags function in cp-demangle.c. The main file, CVE-2025-66866.c, is the actual exploit/PoC: it programmatically constructs a malicious PE/COFF executable containing crafted symbol-table entries and mangled C++ names designed to stress or break demangling. After generating the file (default name: CVE-2025-66866.exe), the program invokes local binutils tools such as objdump, nm, and c++filt via system() to demonstrate whether the target environment crashes, hangs, or behaves normally. The exploit is local-only; there are no network callbacks, remote URLs, or C2-style endpoints. The repository also includes two helper shell scripts: build.sh, which compiles and runs the PoC and performs basic file inspection, and testerpoc.sh, which adds a simple version check and timeout-based testing to help determine whether the installed binutils appears vulnerable. README.md is minimal and provides only the CVE identifier. Overall, the repository’s purpose is to generate a malformed PE file and validate whether local binutils installations—especially version 2.26 and possibly earlier—are susceptible to a demangling-related DoS when processing crafted symbol names.
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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.