CVE-2026-19681

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreHIGH confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-14. a secondary CVSS source baseline 9.9; sources differ by 0.0.

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

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

An authenticated command injection vulnerability exists in Security Center related to file upload processing. An attacker could exploit this issue by uploading a specially crafted file, potentially resulting in arbitrary command execution on the underlying operating system.

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

Published

August 14, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
No patch confirmed yet.
generic

[R1] Security Center Version 6.9.0 Fixes Multiple Vulnerabilities - Security Advisory | Tenable®

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

Vendor Advisories for CVE-2026-19681(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 66× in last 7d / 66× 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-08-21 06:10 UTCGHSA enrichment
  2. 2026-08-21 02:26 UTCEG score recompute
  3. 2026-08-21 02:26 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:42 UTCGHSA enrichment
  6. 2026-08-20 18:58 UTCGHSA enrichment
  7. 2026-08-20 15:14 UTCGHSA enrichment
  8. 2026-08-20 11:30 UTCGHSA enrichment
  9. 2026-08-20 07:46 UTCGHSA enrichment
  10. 2026-08-20 04:02 UTCGHSA enrichment
  11. 2026-08-20 00:18 UTCGHSA enrichment
  12. 2026-08-19 20:33 UTCEG score recompute
  13. 2026-08-19 20:33 UTCGHSA enrichment
  14. 2026-08-19 17:03 UTCEPSS rescore
  15. 2026-08-19 16:48 UTCGHSA enrichment
  16. 2026-08-19 13:54 UTCGHSA enrichment
  17. 2026-08-19 10:09 UTCGHSA enrichment
  18. 2026-08-19 06:20 UTCGHSA enrichment
  19. 2026-08-19 02:35 UTCGHSA enrichment
  20. 2026-08-18 22:47 UTCGHSA enrichment
  21. 2026-08-18 19:03 UTCGHSA enrichment
  22. 2026-08-18 15:18 UTCGHSA enrichment
  23. 2026-08-18 14:58 UTCEG score recompute
  24. 2026-08-18 14:58 UTCGHSA enrichment
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 41 more
  1. 2026-08-18 10:55 UTCGHSA enrichment
  2. 2026-08-18 07:10 UTCGHSA enrichment
  3. 2026-08-18 03:26 UTCGHSA enrichment
  4. 2026-08-17 23:35 UTCGHSA enrichment
  5. 2026-08-17 19:50 UTCGHSA enrichment
  6. 2026-08-17 16:06 UTCEG score recompute
  7. 2026-08-17 16:06 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 12:22 UTCGHSA enrichment
  10. 2026-08-17 08:35 UTCGHSA enrichment
  11. 2026-08-17 04:51 UTCGHSA enrichment
  12. 2026-08-17 01:07 UTCGHSA enrichment
  13. 2026-08-16 21:23 UTCGHSA enrichment
  14. 2026-08-16 17:39 UTCEG score recompute
  15. 2026-08-16 17:39 UTCGHSA enrichment
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 13:55 UTCGHSA enrichment
  18. 2026-08-16 10:10 UTCGHSA enrichment
  19. 2026-08-16 06:26 UTCGHSA enrichment
  20. 2026-08-16 02:43 UTCEG score recompute
  21. 2026-08-16 02:43 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 22:59 UTCGHSA enrichment
  24. 2026-08-15 19:15 UTCGHSA enrichment
  25. 2026-08-15 15:31 UTCGHSA enrichment
  26. 2026-08-15 11:47 UTCGHSA enrichment
  27. 2026-08-15 08:03 UTCGHSA enrichment
  28. 2026-08-15 04:19 UTCEG score recompute
  29. 2026-08-15 04:19 UTCGHSA enrichment
  30. 2026-08-15 04:13 UTCEG score recompute
  31. 2026-08-15 04:13 UTCGHSA enrichment
  32. 2026-08-15 03:04 UTCGHSA enrichment
  33. 2026-08-14 23:20 UTCGHSA enrichment
  34. 2026-08-14 19:36 UTCEG score recompute
  35. 2026-08-14 19:36 UTCGHSA enrichment
  36. 2026-08-14 19:14 UTCEG score recompute
  37. 2026-08-14 19:14 UTCGHSA enrichment
  38. 2026-08-14 18:35 UTCEG score recompute
  39. 2026-08-14 18:35 UTCGHSA enrichment
  40. 2026-08-14 18:09 UTCEG score recompute
  41. 2026-08-14 18:08 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19681?
CVE-2026-19681 is a critical vulnerability published on August 14, 2026. An authenticated command injection vulnerability exists in Security Center related to file upload processing. An attacker could exploit this issue by uploading a specially crafted file, potentially resulting in arbitrary command execution on the underlying operating system.
When was CVE-2026-19681 disclosed?
CVE-2026-19681 was first published in the National Vulnerability Database on August 14, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19681 actively exploited?
CVE-2026-19681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 18.2% of all scored CVEs.
What is the CVSS score of CVE-2026-19681?
CVE-2026-19681 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-19681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19681, 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-19681

Explore →

Is Your Infrastructure Affected by CVE-2026-19681?

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

Start Free Scan →Browse All CVEs