CVE-2026-15228Network attack vector

Cluster-wide configuration denial via duplicate CA IDs

Published Jul 29, 2026 · Updated Jul 29, 2026

Denial of service in Kong Ingress Controller 3.4.0 through 3.4.17 and 3.5.0 through 3.5.10 allows remote authenticated users to halt ingress changes. KIC collects labeled CA-certificate Secrets across watched namespaces and copies attacker-controlled data.id values into cluster-global configuration without rejecting duplicates. Exploitation requires Secret-creation permission in an untrusted watched namespace; a collision makes Kong reject the entire document, blocking configuration updates until the conflict is removed.

CVSS severity7.1
High
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Denial of service in Kong Ingress Controller 3.4.0 through 3.4.17 and 3.5.0 through 3.5.10 allows remote authenticated users to halt ingress changes. KIC collects labeled CA-certificate Secrets across watched namespaces and copies attacker-controlled data.id values into cluster-global configuration without rejecting duplicates. Exploitation requires Secret-creation permission in an untrusted watched namespace; a collision makes Kong reject the entire document, blocking configuration updates until the conflict is removed.

The record

CVE
CVE-2026-15228
Published
Jul 29, 2026
Updated
Jul 29, 2026
Vendor
Kong Inc.
Product
Kong Ingress Controller
Classifications
CWE-400, CWE-862, CAPEC-240, T1499.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 29, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 29, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.4.0 <3.4.18
  2. Affected versionversion=3.5.0 <3.5.11

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Kong Inc. · Kong Ingress Controllerversion=3.4.0 <3.4.18; version=3.5.0 <3.5.11

Published CVSS scores

7.1KongCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-400Uncontrolled Resource Consumption
CWE-862Missing Authorization
CAPEC-240Resource Injection
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo