# CVE-2026-15228: Kong Kubernetes Ingress Controller cluster-wide ingress configuration DoS via CA-certificate ID collision

> A user with namespace Secret privileges can cause cluster-wide ingress configuration denial of service via CA-certificate ID collisions in Kong Kubernetes Ingress Controller.

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-g9h6-h2xj-mf78

## What is CVE-2026-15228?

CVE-2026-15228 is a high-severity denial of service vulnerability, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kong Kubernetes Ingress Controller (KIC) allows a user with namespace-scoped Secret creation privileges to cause a cluster-wide ingress configuration denial of service. 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.

Weakness: CWE-862 (Missing Authorization), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-15228?


## How do I fix CVE-2026-15228?

No fix has been published for CVE-2026-15228 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15228 being exploited?

There is no known exploitation of CVE-2026-15228 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15228 and fix it if it is affected.

What it is: CVE-2026-15228 is a high-severity denial of service vulnerability, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15228 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15228/ (Markdown: https://insights.sbomify.com/CVE-2026-15228/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15228
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15228
- OSV: https://osv.dev/vulnerability/CVE-2026-15228

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15228/
Summaries are generated and may contain mistakes; the official description above is the record.