c++filt crash via heap out-of-bounds read
Published Dec 29, 2025 · Updated Dec 29, 2025
Heap-based buffer overflow in GNU Binutils 2.26 c++filt allows context-dependent attackers to crash the process via crafted demangling input. The gnu_special routine in libiberty/cplus-dem.c reads one byte immediately beyond a two-byte heap allocation while recursively demangling the supplied symbol. The input must reach c++filt or another consumer of the legacy demangler; the demonstrated result is a process abort, with no confidentiality or integrity impact shown.
Summary
What happened
Heap-based buffer overflow in GNU Binutils 2.26 c++filt allows context-dependent attackers to crash the process via crafted demangling input. The gnu_special routine in libiberty/cplus-dem.c reads one byte immediately beyond a two-byte heap allocation while recursively demangling the supplied symbol. The input must reach c++filt or another consumer of the legacy demangler; the demonstrated result is a process abort, with no confidentiality or integrity impact shown.
The record
- CVE
- CVE-2025-66862
- Published
- Dec 29, 2025
- Updated
- Dec 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 29, 2025CVE publishedPublication date reported by the CVE source.
- Dec 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- CRGF-Vul cxxfilt crash3 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo