CVE-2026-17578 (GCVE-0-2026-17578)

Vulnerability from cvelistv5 – Published: 2026-08-05 10:20 – Updated: 2026-08-05 13:07
VLAI
Title
Kong Event Gateway AES-GCM nonce reuse due to missing key rotation enforcement
Summary
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.
Severity
2.3 (Low)
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
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-08-05 13:07 UTC
CWE
  • CWE-323 - Reusing a Nonce, Key Pair in Encryption
Assigner
Kong CNA under the mitre root
CNA scorecard B 82/100 over 27 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Kong Kong Event Gateway Affected: 1.0.0 , < 1.1.2 (semver)
Affected: 1.2.0 , < 1.2.1 (semver)
guessed Create a notification for this product.
Date Public
2026-08-05 17:00
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-17578",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-05T13:07:06.628504Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-08-05T13:07:23.408Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://hub.docker.com/r/kong/kong-event-gateway",
          "defaultStatus": "unaffected",
          "packageName": "kong-event-gateway",
          "product": "Kong Event Gateway",
          "vendor": "Kong",
          "versions": [
            {
              "lessThan": "1.1.2",
              "status": "affected",
              "version": "1.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "1.2.1",
              "status": "affected",
              "version": "1.2.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "datePublic": "2026-08-05T17:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eKong 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.\u003c/p\u003e\u003cp\u003eIf 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.\u003c/p\u003e\u003cp\u003eNew versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached.\u003c/p\u003e"
            }
          ],
          "value": "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.\n\n\n\nIf 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.\n\n\n\nNew versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-97",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-97 Cryptanalysis"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NO",
            "Recovery": "USER",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 2.3,
            "baseSeverity": "LOW",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "LOW",
            "providerUrgency": "AMBER",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "LOW",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "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",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-323",
              "description": "CWE-323: Reusing a Nonce, Key Pair in Encryption",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T10:20:55.471Z",
        "orgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "shortName": "Kong"
      },
      "references": [
        {
          "tags": [
            "release-notes"
          ],
          "url": "https://developer.konghq.com/event-gateway/changelog/"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eUpgrade 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.\u003c/p\u003e"
            }
          ],
          "value": "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."
        }
      ],
      "source": {
        "discovery": "INTERNAL"
      },
      "title": "Kong Event Gateway AES-GCM nonce reuse due to missing key rotation enforcement",
      "x_generator": {
        "engine": "Vulnogram 1.0.4"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
    "assignerShortName": "Kong",
    "cveId": "CVE-2026-17578",
    "datePublished": "2026-08-05T10:20:55.471Z",
    "dateReserved": "2026-07-27T15:40:25.996Z",
    "dateUpdated": "2026-08-05T13:07:23.408Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-17578",
      "date": "2026-11-11",
      "epss": "0.00244",
      "percentile": "0.15794"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "collectionURL": "https://hub.docker.com/r/kong/kong-event-gateway",
                "defaultStatus": "unaffected",
                "packageName": "kong-event-gateway",
                "product": "Kong Event Gateway",
                "vendor": "Kong",
                "versions": [
                  {
                    "lessThan": "1.1.2",
                    "status": "affected",
                    "version": "1.0.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "1.2.1",
                    "status": "affected",
                    "version": "1.2.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "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.\n\n\n\nIf 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.\n\n\n\nNew versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached."
          },
          {
            "lang": "es",
            "value": "Las versiones 1.0.0 a 1.1.1 y 1.2.0 de Kong Event Gateway no aplican la rotaci\u00f3n de claves antes de alcanzar el l\u00edmite de uso recomendado por NIST SP 800-38D para claves de cifrado AES-GCM con nonces aleatorios cuando la funci\u00f3n de cifrado de AWS IAM est\u00e1 habilitada.\n\nSi un productor env\u00eda mensajes a una tasa alta y sostenida sin rotaci\u00f3n de claves, lo que solo ocurre al reiniciar la instancia de Kong Event Gateway, la probabilidad de una colisi\u00f3n de nonce se vuelve no despreciable. Un consumidor autorizado que detecta una colisi\u00f3n de nonce puede recuperar partes del texto sin cifrar de los mensajes afectados.\n\nLas nuevas versiones 1.1.2 y 1.2.1 aplican la rotaci\u00f3n autom\u00e1tica de claves antes de que se alcance el l\u00edmite de uso recomendado."
          }
        ],
        "id": "CVE-2026-17578",
        "lastModified": "2026-10-23T21:10:00.157",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NO",
                "Recovery": "USER",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 2.3,
                "baseSeverity": "LOW",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "AMBER",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "LOW",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:X/RE:X/U:Amber",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "LOW",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-17578",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-05T13:07:06.628504Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-08-05T11:16:25.197",
        "references": [
          {
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "url": "https://developer.konghq.com/event-gateway/changelog/"
          }
        ],
        "sourceIdentifier": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "vulnStatus": "Awaiting Analysis",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-323"
              }
            ],
            "source": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "type": "Secondary"
          }
        ]
      }
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-17578",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-08-05T13:07:06.628504Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-08-05T13:07:18.142Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "collectionURL": "https://hub.docker.com/r/kong/kong-event-gateway",
              "defaultStatus": "unaffected",
              "packageName": "kong-event-gateway",
              "product": "Kong Event Gateway",
              "vendor": "Kong",
              "versions": [
                {
                  "lessThan": "1.1.2",
                  "status": "affected",
                  "version": "1.0.0",
                  "versionType": "semver"
                },
                {
                  "lessThan": "1.2.1",
                  "status": "affected",
                  "version": "1.2.0",
                  "versionType": "semver"
                }
              ]
            }
          ],
          "datePublic": "2026-08-05T17:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eKong 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.\u003c/p\u003e\u003cp\u003eIf 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.\u003c/p\u003e\u003cp\u003eNew versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached.\u003c/p\u003e"
                }
              ],
              "value": "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.\n\n\n\nIf 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.\n\n\n\nNew versions 1.1.2 and 1.2.1 enforce automatic key rotation before the recommended usage limit is reached."
            }
          ],
          "impacts": [
            {
              "capecId": "CAPEC-97",
              "descriptions": [
                {
                  "lang": "en",
                  "value": "CAPEC-97 Cryptanalysis"
                }
              ]
            }
          ],
          "metrics": [
            {
              "cvssV4_0": {
                "Automatable": "NO",
                "Recovery": "USER",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "NETWORK",
                "baseScore": 2.3,
                "baseSeverity": "LOW",
                "exploitMaturity": "NOT_DEFINED",
                "privilegesRequired": "LOW",
                "providerUrgency": "AMBER",
                "subAvailabilityImpact": "NONE",
                "subConfidentialityImpact": "LOW",
                "subIntegrityImpact": "NONE",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "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",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "LOW",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-323",
                  "description": "CWE-323: Reusing a Nonce, Key Pair in Encryption",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-08-05T10:20:55.471Z",
            "orgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
            "shortName": "Kong"
          },
          "references": [
            {
              "tags": [
                "release-notes"
              ],
              "url": "https://developer.konghq.com/event-gateway/changelog/"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "supportingMedia": [
                {
                  "base64": false,
                  "type": "text/html",
                  "value": "\u003cp\u003eUpgrade 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.\u003c/p\u003e"
                }
              ],
              "value": "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."
            }
          ],
          "source": {
            "discovery": "INTERNAL"
          },
          "title": "Kong Event Gateway AES-GCM nonce reuse due to missing key rotation enforcement",
          "x_generator": {
            "engine": "Vulnogram 1.0.4"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "02762ae7-200e-4b20-9b2b-a77d5b8fc4cb",
        "assignerShortName": "Kong",
        "cveId": "CVE-2026-17578",
        "datePublished": "2026-08-05T10:20:55.471Z",
        "dateReserved": "2026-07-27T15:40:25.996Z",
        "dateUpdated": "2026-08-05T13:07:23.408Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.