Skip to main content
VulnerabilityPublished

CVE-2026-19542: Glibc · Stack-based out-of-bounds write in tdelete during tree rebalancing

Affects glibcSource GCVE Database

0
Compare
Authoritative record:CVE-2026-19542· Medium 5.6

Not known to be exploited · CVSS 5.6 Medium : upgrade to 2.39_2 when convenient.

Data as of 18 Nov 2026, 17:49 UTC

CVSS 3.1 base score
5.6Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.39_2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade glibc to 2.39_2.

Affected software

ProductAffectedFixed in
Homebrewglibcpkg:brew/glibcOther threatsAffected
  • <2.39_2
Fixed in
  • 2.39_2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Calling tdelete on a sufficiently deep tree in the GNU C Library version 2.1 to 2.44 may write one pointer past the end of an alloca-allocated array on the stack, which may crash the application. The tdelete implementation keeps an explicit stack of parent nodes for rebalancing, which is grown as needed while descending the tree. Two rebalancing branches push an additional entry without checking the capacity, and write past the array when the stack is exactly full. Triggering this requires a node at a depth of exactly 40 (or 40 plus a multiple of 20), which implies a tree with at least a million nodes, so an attacker must drive a large number of insertions and deletions through an application that uses tsearch and tdelete. The written value is a pointer into a tree node and is not directly attacker controlled. No affected application in common distributions has been identified.

References

Community reviews

Loading reviews…