CVE-2026-17578: CWE-323: Reusing a Nonce, Key Pair in Encryption in Kong Kong Event Gateway
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.
AI Analysis
Technical Summary
Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 do not enforce key rotation before reaching the NIST SP 800-38D recommended usage limit for AES-GCM encryption keys with random nonces when the AWS IAM encryption feature is enabled. Sustained high-rate message production without key rotation (which only occurs on reboot) increases the probability of nonce collisions. An authorized consumer who detects a nonce collision can recover parts of plaintext from the affected messages. Newer versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached, addressing the vulnerability.
Potential Impact
If exploited, an authorized consumer could recover parts of plaintext from messages encrypted with reused nonces due to nonce collisions. This compromises message confidentiality partially. The vulnerability requires sustained high-rate message production without key rotation and authorized consumer access. There are no known exploits in the wild. The CVSS score is low (2.3), reflecting limited impact and exploitability.
Mitigation Recommendations
A patch is available and included in Kong Event Gateway versions 1.1.2 and 1.2.1, which enforce automatic key rotation before reaching the recommended usage limit. Users should upgrade to these versions or later. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with Kong's advisory for cloud service patch status and ensure their instances are updated accordingly.
CVE-2026-17578: CWE-323: Reusing a Nonce, Key Pair in Encryption in Kong Kong Event Gateway
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.
CVSS v4.0
Score 2.3low
Affected software
pkg:github/kong/event-gatewayRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 do not enforce key rotation before reaching the NIST SP 800-38D recommended usage limit for AES-GCM encryption keys with random nonces when the AWS IAM encryption feature is enabled. Sustained high-rate message production without key rotation (which only occurs on reboot) increases the probability of nonce collisions. An authorized consumer who detects a nonce collision can recover parts of plaintext from the affected messages. Newer versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached, addressing the vulnerability.
Potential Impact
If exploited, an authorized consumer could recover parts of plaintext from messages encrypted with reused nonces due to nonce collisions. This compromises message confidentiality partially. The vulnerability requires sustained high-rate message production without key rotation and authorized consumer access. There are no known exploits in the wild. The CVSS score is low (2.3), reflecting limited impact and exploitability.
Mitigation Recommendations
A patch is available and included in Kong Event Gateway versions 1.1.2 and 1.2.1, which enforce automatic key rotation before reaching the recommended usage limit. Users should upgrade to these versions or later. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with Kong's advisory for cloud service patch status and ensure their instances are updated accordingly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Kong
- Date Reserved
- 2026-07-27T15:40:25.996Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a731a7fbf8831d539c95c4d
Added to database: 08/05/2026, 11:11:59 UTC
Last enriched: 08/05/2026, 11:28:04 UTC
Last updated: 08/06/2026, 02:06:54 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.