CVE-2026-68491

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.4Exploit: None knownExposed: 0

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

An insufficient check allowed for the overwrite of arbitrary files via a symlink.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity94% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-68491(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 42× in last 7d / 42× 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-20 14:10 UTCGHSA enrichment
  2. 2026-09-20 10:20 UTCGHSA enrichment
  3. 2026-09-20 06:29 UTCGHSA enrichment
  4. 2026-09-20 02:36 UTCGHSA enrichment
  5. 2026-09-19 22:45 UTCGHSA enrichment
  6. 2026-09-19 18:55 UTCEG score recompute
  7. 2026-09-19 18:55 UTCGHSA enrichment
  8. 2026-09-19 15:04 UTCGHSA enrichment
  9. 2026-09-19 11:11 UTCGHSA enrichment
  10. 2026-09-19 07:20 UTCGHSA enrichment
  11. 2026-09-19 03:29 UTCGHSA enrichment
  12. 2026-09-18 23:39 UTCGHSA enrichment
  13. 2026-09-18 19:48 UTCEG score recompute
  14. 2026-09-18 19:48 UTCGHSA enrichment
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 17:35 UTCGHSA enrichment
  17. 2026-09-18 13:45 UTCGHSA enrichment
  18. 2026-09-18 09:54 UTCGHSA enrichment
  19. 2026-09-18 06:03 UTCGHSA enrichment
  20. 2026-09-18 02:12 UTCGHSA enrichment
  21. 2026-09-17 22:21 UTCEG score recompute
  22. 2026-09-17 22:21 UTCGHSA enrichment
  23. 2026-09-17 18:30 UTCGHSA enrichment
  24. 2026-09-17 14:38 UTCGHSA enrichment
  25. 2026-09-17 10:47 UTCGHSA enrichment
Show 17 more
  1. 2026-09-17 06:57 UTCGHSA enrichment
  2. 2026-09-17 03:07 UTCGHSA enrichment
  3. 2026-09-16 23:16 UTCGHSA enrichment
  4. 2026-09-16 19:25 UTCEG score recompute
  5. 2026-09-16 19:25 UTCGHSA enrichment
  6. 2026-09-16 18:26 UTCEG score recompute
  7. 2026-09-16 18:26 UTCGHSA enrichment
  8. 2026-09-16 17:15 UTCEG score recompute
  9. 2026-09-16 17:14 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 12:42 UTCGHSA enrichment
  12. 2026-09-16 08:52 UTCGHSA enrichment
  13. 2026-09-16 05:01 UTCGHSA enrichment
  14. 2026-09-16 01:09 UTCGHSA enrichment
  15. 2026-09-15 21:18 UTCEG score recompute
  16. 2026-09-15 21:03 UTCEG score recompute
  17. 2026-09-15 21:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68491?
CVE-2026-68491 is a critical vulnerability published on September 15, 2026. An insufficient check allowed for the overwrite of arbitrary files via a symlink.
When was CVE-2026-68491 disclosed?
CVE-2026-68491 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68491 actively exploited?
CVE-2026-68491 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 74.0% of all scored CVEs.
What is the CVSS score of CVE-2026-68491?
CVE-2026-68491 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-68491?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68491, 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-68491

Explore →

Is Your Infrastructure Affected by CVE-2026-68491?

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