CVE-2026-86805

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-09-22. a secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 23, 2026

Advisory Details (2)

Auto-updated Sep 22, 2026
No patch confirmed yet.
generic

34360 – (CVE-2026-86805) TOCTOU race condition in processing RPATH with $ORIGIN DST for setuid/setgid binaries (CVE-2026-86805)

https://sourceware.org/bugzilla/show_bug.cgi?id=34360

Vendor Advisories for CVE-2026-86805(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 03:50 UTCEG score recompute
  2. 2026-09-24 03:50 UTCGHSA enrichment
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-23 04:41 UTCEG score recompute
  5. 2026-09-23 04:41 UTCGHSA enrichment
  6. 2026-09-23 04:03 UTCEG score recompute
  7. 2026-09-23 04:03 UTCGHSA enrichment
  8. 2026-09-22 20:12 UTCEG score recompute
  9. 2026-09-22 20:12 UTCGHSA enrichment
  10. 2026-09-22 17:36 UTCEG score recompute
  11. 2026-09-22 16:52 UTCEG score recompute 0.70
  12. 2026-09-22 16:49 UTCMITRE cvelistV5CVSS v3 → 6.3 · severity → MEDIUM
  13. 2026-09-22 16:19 UTCEG score recompute
  14. 2026-09-22 16:00 UTCEG score recompute
  15. 2026-09-22 15:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86805?
CVE-2026-86805 is a medium vulnerability published on September 22, 2026. 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 DTRPATH for setuid/setgid (ATSECURE) programs, glibc validates the lexically…
When was CVE-2026-86805 disclosed?
CVE-2026-86805 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86805 actively exploited?
CVE-2026-86805 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-86805?
CVE-2026-86805 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-86805?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86805, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-86805

Explore →

Is Your Infrastructure Affected by CVE-2026-86805?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.