Skip to main content
VulnerabilityPublished

CVE-2026-16543: kong-operator · Missing Authorization

Affects kong-operatorSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High · fixed in 2.2.3 : patch kong-operator soon.

Data as of 27 Oct 2026, 17:11 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.3, 2.1.9, 2.0.11
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Kong/kong-operator to 2.2.3, 2.1.9 or 2.0.11.

Affected software

ProductAffectedFixed in
GitHubKong/kong-operatorpkg:github/Kong/kong-operatorOther threatsAffected
  • >=2.2.0 <2.2.3
  • >=2.1.0 <2.1.9
  • <2.0.11
Fixed in
  • 2.2.3
  • 2.1.9
  • 2.0.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict Secret creation privileges carefully and monitor for suspicious Secret creation activities that could lead to duplicate CA-certificate IDs. Consider limiting label selectors or namespace watching scope if configurable.

Description

Kong Operator's embedded Kong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. The embedded KIC collects CA-certificate Secrets across all watched namespaces using a label selector alone, without ingress-class or namespace restrictions. The CA-certificate primary key is derived from a user-supplied field in the Secret. Duplicate CA-certificate IDs cause Kong Gateway to reject the entire configuration document and halting all ingress changes cluster-wide.

References

Community reviews

Loading reviews…