CVE-2026-86805
Last modified
CVE-2026-86805 is a medium-severity vulnerability rated 6.3/10 on the CVSS scale. A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path.
Description
A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where the Linux fs.protected_hardlinks sysctl is disabled, a local attacker who hard-links such a program into an attacker-controlled directory and wins a race to replace an intermediate path component with a symbolic link can direct the loader outside the trusted directory, causing it to load an attacker-controlled shared object and execute arbitrary code with the elevated privileges of the program. Exploitation requires an installed setuid or setgid binary whose DT_RPATH uses $ORIGIN followed by ".." traversal that normalizes into a trusted directory, and the ability to hard-link that binary and win the race by swapping a path component for a symbolic link. Major Linux-based OS distributions ship with fs.protected_hardlinks enabled by default and mitigate the vulnerability.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| The GNU C Library | glibc | >= 2.14, < 2.45 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-86805?
How severe is CVE-2026-86805?
How do I fix CVE-2026-86805?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-86796The Hide My WP Ghost WordPress plugin before 7.0.11 does not…5.3
- CVE-2026-8680Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-86800The Hide My WP Ghost WordPress plugin before 7.0.11 does not…5.3
- CVE-2026-86801The To Do List Member WordPress plugin from 1.4 through 1.6 …8.8
- CVE-2026-86802The To Do List Member WordPress plugin through 1.6 does not …3.7
- CVE-2026-86804A vulnerability was identified in seakee CPA-Manager-Plus up…5.3
- CVE-2026-86806A weakness has been identified in opengeos GeoLibre up to 2.…7.3
- CVE-2026-86808A security vulnerability has been detected in moltis-org mol…7.3
- CVE-2026-86809The Persian Elementor WordPress plugin from 2.7.10 before 2.…5.3
- CVE-2026-8681The Essential Chat Support plugin for WordPress is vulnerabl…5.3
- CVE-2026-86810A vulnerability was detected in Open-Web-Analytics up to 1.9…7.3
- CVE-2026-86812The WPCafe WordPress plugin before 3.0.18 does not correctl…6.5
Are you affected by CVE-2026-86805?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
