CVE-2026-24512
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security issue was discovered in ingress-nginx where the `rules.http.paths.path` Ingress field can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe ingress-nginx controller vulnerability allows injection of arbitrary nginx configuration via the `rules.http.paths.path` field in Ingress resources. This enables attackers to achieve arbitrary code execution in the controller's context and exfiltrate any Kubernetes Secrets accessible to the controller (cluster-wide by default).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ingress-nginx installationRun: kubectl get pods -n ingress-nginx -o jsonpath='{.items[*].spec.containers[*].image}' to find the ingress-nginx controller imageAffected if The image contains 'ingress-nginx' and the version is unpatched against CVE-2026-24512
-
Determine ingress-nginx versionRun: kubectl get deployment -n ingress-nginx ingress-nginx-controller -o jsonpath='{.spec.template.spec.containers[0].image}' and parse the image tag versionAffected if The version matches any unpatched version range for CVE-2026-24512 (compare against known affected versions)
-
List all Ingress resources cluster-wideRun: kubectl get ingress --all-namespaces -o json to retrieve all Ingress objectsAffected if Any Ingress resource exists in the cluster (the vulnerability applies to any Ingress with injectable path values)
-
Inspect Ingress path fields for injection patternsExamine the 'spec.rules[].http.paths[].path' field in each Ingress for patterns like include statements, semicolons in unusual positions, or path traversal sequencesAffected if Any Ingress resource contains path values with nginx configuration syntax, unexpected characters, or suspicious patterns that could inject nginx directives
You are affected if ingress-nginx controller is running and any Ingress resource in your cluster contains path values in the rules.http.paths.path field that could be interpreted as nginx configuration injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately restrict the ingress-nginx controller's RBAC permissions to limit secret access, validate and normalize Ingress path fields to prevent injection, and monitor for anomalous Ingress resource creation or modification.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data