Application crash via tdelete parent-stack overflow
Published Sep 14, 2026 · Updated Sep 14, 2026
Out-of-bounds write in glibc 2.1 through 2.44 allows local users to crash an application through a deeply populated tsearch tree. During tdelete rebalancing, two branches push a parent-node pointer after the dynamically grown alloca array reaches capacity, writing one slot past its end. Triggering requires a depth of exactly 40 or 40 plus a multiple of 20, at least about one million nodes, and control over many insertions and deletions; the pointer value is not directly controlled.
Summary
What happened
Out-of-bounds write in glibc 2.1 through 2.44 allows local users to crash an application through a deeply populated tsearch tree. During tdelete rebalancing, two branches push a parent-node pointer after the dynamically grown alloca array reaches capacity, writing one slot past its end. Triggering requires a depth of exactly 40 or 40 plus a multiple of 20, at least about one million nodes, and control over many insertions and deletions; the pointer value is not directly controlled.
The record
- CVE
- CVE-2026-19542
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- The GnuPG Project
- Product
- glibc
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.1 <=2.44
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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