CVE-2026-17578: Kong Event Gateway AES-GCM nonce reuse due to missing key rotation enforcement
Kong · Kong Event Gateway
Vendor fix available · Affected: Kong Event Gateway · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 15% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Kong · Kong Event Gatewayfrom 1.0.0 before 1.1.2; from 1.2.0 before 1.2.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Kong
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-17578 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.