Skip to main content
VulnerabilityPublished

CVE-2026-95818: Glibc · AT_SECURE program buffer overflow via $ORIGIN processing

Affects glibcSource GCVE Database

0
Compare
Authoritative record:CVE-2026-95818· Low 3.6

Not known to be exploited · CVSS 3.6 Low : upgrade to 2.39_2 when convenient.

Data as of 18 Nov 2026, 17:49 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 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

A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs. When such a program's DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or '/' the loader both reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer. The corrupted loader stack can lead to a loader crash (denial of service) and limited disclosure of process memory.

References

Community reviews

Loading reviews…