CVE-2026-17578: Kong Event Gateway AES-GCM nonce reuse due to missing key rotation enforcement
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Kong Event Gatewayto a version that resolves this vulnerability.Fixed in 1.1.2 - Upgrade
Upgrade
Kong Event Gatewayto a version that resolves this vulnerability.Fixed in 1.2.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-17578?
CVE-2026-17578 has a risk score of 37, indicating a moderate severity vulnerability.
How do I fix CVE-2026-17578?
To fix CVE-2026-17578, ensure that the Kong Event Gateway is upgraded to a version that enforces key rotation for AES-GCM encryption.
What versions of Kong Event Gateway are affected by CVE-2026-17578?
Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 are affected by CVE-2026-17578.
What is the impact of CVE-2026-17578 on AWS IAM encryption?
CVE-2026-17578 allows for nonce reuse in AES-GCM encryption, potentially compromising the security of messages sent via AWS IAM.
How can I monitor for exploitation of CVE-2026-17578?
Monitoring for unusual message rates and encrypted data patterns can help identify potential exploitation of CVE-2026-17578.