CVE-2026-17578

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (14th percentile of EPSS-scored CVEs). 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 — 3 sources updated this week
2.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 2.3Exploit: None knownExposed services: Not assessed

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

Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 do not enforce key rotation before reaching NIST SP 800-38D recommended usage limit for AES-GCM encryption keys with random nonces when the AWS IAM encryption feature is enabled.

If a producer sends messages at a sustained high rate without key rotation, which only occurs on reboot of the Kong Event Gateway instance, the probability of a nonce collision becomes non-negligible. An authorized consumer who detects a nonce collision can recover parts of plaintext from the affected messages.

New versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached.

CVSS v3
2.3
EG Score
2.3LOWmedium confidence
EG Risk
10
EG Risk 10/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
Severity23% × 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.2%
EPSS %ILE
14th
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 5, 2026

Last Modified

August 31, 2026

References (1)

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17578?
CVE-2026-17578 is a low vulnerability published on August 5, 2026. Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 do not enforce key rotation before reaching NIST SP 800-38D recommended usage limit for AES-GCM encryption keys with random nonces when the AWS IAM encryption feature is enabled. If a producer sends messages at a sustained high rate without…
When was CVE-2026-17578 disclosed?
CVE-2026-17578 was first published on August 5, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17578 actively exploited?
CVE-2026-17578 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17578?
CVE-2026-17578 has a CVSS base score of 2.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17578?
No fix for CVE-2026-17578 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-17578 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-17578?

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

Book a Demo →Browse All CVEs