cxxfilt crash via null-pointer read
Published Dec 29, 2025 · Updated Dec 29, 2025
NULL-pointer dereference in cxxfilt in GNU Binutils 2.26 allows local users to crash the process with crafted demangling input. In d_print_comp_inner in libiberty/cp-demangle.c, a read through a null pointer at line 4442 raises a segmentation fault while cxxfilt renders the malformed symbol. An attacker must cause a user or local workflow to pass the crafted input to cxxfilt; the demonstrated consequence is termination of that process.
Summary
What happened
NULL-pointer dereference in cxxfilt in GNU Binutils 2.26 allows local users to crash the process with crafted demangling input. In d_print_comp_inner in libiberty/cp-demangle.c, a read through a null pointer at line 4442 raises a segmentation fault while cxxfilt renders the malformed symbol. An attacker must cause a user or local workflow to pass the crafted input to cxxfilt; the demonstrated consequence is termination of that process.
The record
- CVE
- CVE-2025-66864
- Published
- Dec 29, 2025
- Updated
- Dec 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499.004
- 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
- crash5 cxxfilt 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