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

> An authorized consumer can recover plaintext from messages if AES-GCM nonce collisions occur due to missing key rotation in Kong Event Gateway.

- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-v6xc-r9wm-438j

## What is CVE-2026-17578?

CVE-2026-17578 is a low-severity vulnerability in Kong Event Gateway, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-323 (Reusing a Nonce, Key Pair in Encryption)

## Which versions are affected by CVE-2026-17578?


## How do I fix CVE-2026-17578?

No fix has been published for CVE-2026-17578 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-17578 being exploited?

There is no known exploitation of CVE-2026-17578 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17578 and fix it if it is affected.

What it is: CVE-2026-17578 is a low-severity vulnerability in Kong Event Gateway, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17578 in the wild and no public exploit code.

Affected product: Kong Event Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-17578/ (Markdown: https://insights.sbomify.com/CVE-2026-17578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17578
- OSV: https://osv.dev/vulnerability/CVE-2026-17578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-17578/
Summaries are generated and may contain mistakes; the official description above is the record.