CVE-2026-64881

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

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

The audit file upload handler does not sanitize filenames, allowing shell metacharacters to flow into system command execution. This input validation failure enables command injection when chained with a related vulnerability.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
70%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 21, 2026
Patch available.
generic Patch Available

[R2] Stand-alone Security Patch Available for Tenable Security Center Versions 6.6.0, 6.7.2 and 6.8.0: SC202607.1 - Security Advisory | Tenable®

https://www.tenable.com/security/tns-2026-19

Vendor Advisories for CVE-2026-64881(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 26× in last 7d / 34× 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-07-30 05:24 UTCEG score recompute
  2. 2026-07-30 05:24 UTCGHSA enrichment
  3. 2026-07-30 01:30 UTCEPSS rescore
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-29 17:15 UTCGHSA enrichment
  6. 2026-07-29 05:08 UTCGHSA enrichment
  7. 2026-07-28 17:02 UTCEG score recompute
  8. 2026-07-28 17:02 UTCGHSA enrichment
  9. 2026-07-28 15:37 UTCEPSS rescore
  10. 2026-07-28 04:52 UTCGHSA enrichment
  11. 2026-07-27 16:44 UTCEG score recompute
  12. 2026-07-27 16:44 UTCGHSA enrichment
  13. 2026-07-27 14:14 UTCEPSS rescore
  14. 2026-07-27 04:33 UTCGHSA enrichment
  15. 2026-07-26 16:26 UTCEG score recompute
  16. 2026-07-26 16:25 UTCGHSA enrichment
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 14:54 UTCEPSS rescore
  19. 2026-07-26 04:19 UTCEG score recompute
  20. 2026-07-26 04:19 UTCGHSA enrichment
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-25 14:18 UTCEPSS rescore
  23. 2026-07-24 14:18 UTCEPSS rescore
  24. 2026-07-24 14:18 UTCEPSS rescore
  25. 2026-07-23 14:18 UTCEPSS rescore
Show 9 more
  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:22 UTCEG score recompute
  3. 2026-07-22 22:59 UTCEG score recompute
  4. 2026-07-22 22:59 UTCGHSA enrichment
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-21 21:24 UTCEG score recompute
  8. 2026-07-21 20:45 UTCEG score recompute
  9. 2026-07-21 20:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64881?
CVE-2026-64881 is a high vulnerability published on July 21, 2026. The audit file upload handler does not sanitize filenames, allowing shell metacharacters to flow into system command execution. This input validation failure enables command injection when chained with a related vulnerability.
When was CVE-2026-64881 disclosed?
CVE-2026-64881 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64881 actively exploited?
CVE-2026-64881 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 29.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64881?
CVE-2026-64881 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-64881?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64881, 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-64881

Explore →

Is Your Infrastructure Affected by CVE-2026-64881?

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

Start Free Scan →Browse All CVEs