CVE-2026-11617

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-08-19. A secondary CVSS source baseline 3.1; sources differ by 0.0.

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

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

Tanium addressed a compression bomb vulnerability in Findings.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/100CISA SSVC

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
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

September 1, 2026

References (1)

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-11617?
CVE-2026-11617 is a low vulnerability published on August 19, 2026. Tanium addressed a compression bomb vulnerability in Findings.
When was CVE-2026-11617 disclosed?
CVE-2026-11617 was first published on August 19, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11617 actively exploited?
CVE-2026-11617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11617?
CVE-2026-11617 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11617?
No fix for CVE-2026-11617 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-11617 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-11617?

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

Book a Demo →Browse All CVEs