Skip to content
major vulnerability· requires attention

Widely used ingress-nginx controller; RCE and secret leakage threaten core infra.

Infrastructure

CVE-2026-3288

8.8
High
EPSS 6%Patch availableMar 10, 2026

Ingress-nginx rewrite-target allows config injection, enabling RCE and secret exposure.

common questions

Is CVE-2026-3288 being exploited?

Not confirmed. CVE-2026-3288 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 6.3% probability of exploitation in the next 30 days.

How severe is CVE-2026-3288?

CVE-2026-3288 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-3288?

Yes. A fix has been recorded for CVE-2026-3288. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-3288 affect?

CVE-2026-3288 affects ingress-nginx, Kubernetes Ingress Controller, Kubernetes clusters using ingress-nginx. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-3288?

Upgrade to patched ingress-nginx version

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ingress-nginxKubernetes Ingress ControllerKubernetes clusters using ingress-nginx
impact

RCE via rewrite-target annotation; may expose cluster Secrets accessible to the controller.

action required

Patch when possible

affected versions
Kubernetes ingress-nginx
  • affected< 1.13.8
  • affected< 1.14.4
  • affected< 1.15.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free