CVE-2026-4342 json
ingress-nginx comment-based nginx configuration injection
published 7mo ago modified 4mo ago also EUVD-2026-13343 , GHSA-f53h-mxv9-cp98 , GO-2026-4796
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 0
- none known
Summary
A security issue was discovered in ingress-nginx where a combination of Ingress annotations 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
- go k8s.io/ingress-nginx 0.0.0-20260319175635-5183b7d86137
- Kubernetes ingress-nginx 1.13.9, 1.14.5, 1.15.1
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260326T203309-150000.1.155.2
suse advisories SUSE-SU-2026:1135-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2026-4342 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 7mo ago
Exploit prediction
1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | k8s.io/ingress-nginx | <0.0.0-20260319175635-5183b7d86137 |
0.0.0-20260319175635-5183b7d86137 |
Affected products
- Kubernetes ingress-nginx
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
github.com
/kubernetes/ingress-nginx/commit/5183b7d861377a9a2f6d2acaf44f8f6abd5cd0aa
web
-
github.com
/kubernetes/kubernetes/issues/137893
web, issue-tracking
-
openwall.com
/lists/oss-security/2026/03/19/9
web, mailing-list, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-4342
advisory
-
github.com
/kubernetes/ingress-nginx
package
-
github.com
/advisories/GHSA-f53h-mxv9-cp98
advisory
Sources
- CVE List CVE-2026-4342
- GitHub Advisory GHSA-f53h-mxv9-cp98
- NVD CVE-2026-4342
- OSV GO-2026-4796
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.