Process crash via recursive demangler stack exhaustion
Published Dec 29, 2025 · Updated Dec 29, 2025
Stack overflow in GNU Binutils 2.26 c++filt allows attackers to crash the utility by processing a crafted PE file. The d_print_comp_inner routine in libiberty/cp-demangle.c recursively formats attacker-controlled demangling structures until the process stack is exhausted. The file must be passed to c++filt, and the demonstrated consequence is process termination rather than code execution or data access.
Summary
What happened
Stack overflow in GNU Binutils 2.26 c++filt allows attackers to crash the utility by processing a crafted PE file. The d_print_comp_inner routine in libiberty/cp-demangle.c recursively formats attacker-controlled demangling structures until the process stack is exhausted. The file must be passed to c++filt, and the demonstrated consequence is process termination rather than code execution or data access.
The record
- CVE
- CVE-2025-66865
- Published
- Dec 29, 2025
- Updated
- Dec 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- unauthenticated
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.
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 poc4 reproducerproof 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