CVE-2026-17578 PUBLISHED

Kong Event Gateway AES-GCM nonce reuse due to missing key rotation enforcement

Assigner: Kong
Reserved: 27.07.2026 Published: 05.08.2026 Updated: 05.08.2026

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.

Metrics

CVSS 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
CVSS Score: 2.3

Product Status

Vendor Kong
Product Kong Event Gateway
Versions Default: unaffected
  • affected from 1.0.0 to 1.1.2 (excl.)
  • affected from 1.2.0 to 1.2.1 (excl.)

Solutions

Upgrade Kong Event Gateway to version 1.1.2 (for the 1.1.x branch or 1.0.x which is no longer supported) or 1.2.1 (for the 1.2.x branch). These versions enforce automatic key rotation before the NIST-recommended usage limit is reached.

References

Problem Types

  • CWE-323: Reusing a Nonce, Key Pair in Encryption CWE

Impacts

  • CAPEC-97 Cryptanalysis