Quick answers
- Is CVE-2026-86805 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86805 being exploited in the wild.
- How severe is CVE-2026-86805?
- Medium severity, with a CVSS score of 6.3, published 22 September 2026.
- Which products and versions are affected?
- Gnu C Library (glibc) 2.14 through 2.44.
- Is there a fix for CVE-2026-86805?
- A patch was published on 2026: Fix included in glibc 2.45 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86805 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-86805?
- Check whether you run Gnu C Library (glibc) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A TOCTOU race condition in glibc's ld.so during $ORIGIN expansion in DT_RPATH for AT_SECURE processes allows local privilege escalation. The loader validates the normalized path against trusted directories but opens the raw, un-normalized path, permitting traversal sequences like "/tmp/a/b/../../../usr/lib". On systems with fs.protected_hardlinks disabled, an attacker can hard-link the setuid/setgid binary and race to replace path components with symlinks, redirecting the loader to load attacker-controlled shared objects.
Affected products
- GNU C Library (glibc) 2.14 through 2.44
Timeline
- 2026-07-06: disclosed
- 2026: patched: Fix included in glibc 2.45