CVE-2026-17578: Kong Event Gateway · Reusing a Nonce, Key Pair in Encryption
Affects Kong Event GatewaySource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 1.2.1 or 1.1.2 when convenient.
Data as of 3 Nov 2026, 22:58 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.2.1, 1.1.2
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:AmberExploitation evidence
Disclosed: evidence found.
CVE published 5 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade Kong Event Gateway to 1.2.1 or 1.1.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| KongKong Event Gateway | Affected
| Fixed in
|
| KongKong Event Gateway | Affected
| Fixed in
|
AI-suggested
A fix is available in Kong Event Gateway versions 1.1.2 and 1.2.1, which enforce automatic key rotation before the recommended usage limit for AES-GCM keys is reached. Users should upgrade to these versions to mitigate the vulnerability. Since this is a cloud service, the vendor manages remediation for the cloud-hosted service; users should verify with Kong's advisory for current status.
Description
Kong Event Gateway versions 1.0.0 through 1.1.1 and 1.2.0 have a vulnerability where key rotation is not enforced before reaching the NIST recommended usage limit for AES-GCM encryption keys with random nonces when AWS IAM encryption is enabled. This can lead to nonce reuse, increasing the risk of nonce collisions. An authorized consumer detecting such a collision could recover parts of plaintext from affected messages. Versions 1.1.2 and 1.2.1 address this issue by enforcing automatic key rotation before the usage limit is reached.