Process crash via invalid discriminator read
Published Dec 29, 2025 · Updated Dec 29, 2025
A segmentation fault in GNU Binutils 2.26 c++filt allows local users to crash the process by supplying crafted demangler input. The d_discriminator parser in libiberty/cp-demangle.c performs an invalid high-address read while decoding a discriminator in the mangled name. Triggering the flaw requires passing the crafted input to c++filt or another caller of the affected demangler, and the demonstrated consequence is process termination.
Summary
What happened
A segmentation fault in GNU Binutils 2.26 c++filt allows local users to crash the process by supplying crafted demangler input. The d_discriminator parser in libiberty/cp-demangle.c performs an invalid high-address read while decoding a discriminator in the mangled name. Triggering the flaw requires passing the crafted input to c++filt or another caller of the affected demangler, and the demonstrated consequence is process termination.
The record
- CVE
- CVE-2025-66863
- Published
- Dec 29, 2025
- Updated
- Dec 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499
- 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.
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.
Public exploit references
- c++filt crash2 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