Skip to content
Fencer Intel
high 8.8

CVE-2026-3288 json

ingress-nginx rewrite-target nginx configuration injection

published 8mo ago modified 4mo ago also EUVD-2026-10360

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
7.0%
EPSS 7.0% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/rewrite-target` Ingress annotation 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.)

Patch / fix

  • Kubernetes ingress-nginx 1.13.8, 1.14.4, 1.15.0

Is CVE-2026-3288 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
6mo ago

Exploit prediction

6.99% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/bvabhishek/CVE-2026-3288-lab referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Kubernetes ingress-nginx

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.