CVE-2026-4342· NVD / CVE Program· CNA kubernetes

ingress-nginx comment-based nginx configuration injection

Noroxi assessment

Priority: Monitor (action score 35/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.62% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Kubernetes ingress-nginx 1.13.9, 1.14.5, 1.15.1.

Low priority for now. Upgrade to Kubernetes ingress-nginx 1.13.9, 1.14.5, 1.15.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.)

HighCVSS 8.8 · v3.1—Proof of concept Fix available

Published: Mar 19, 2026
Updated: Jun 17, 2026
EPSS: 0.6% · 49th percentile
CWE: CWE-20

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.8
CNA · kubernetes: 8.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
kubernetes	nginx ingress controller	cpe:2.3:a:kubernetes:nginx_ingress_controller

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

kubernetes nginx ingress controllerbefore 1.13.9
kubernetes nginx ingress controller1.14.0 and later · before 1.14.5
kubernetes nginx ingress controller1.15.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.

Kubernetes ingress-nginx
- before 1.13.9affected · semver
- before 1.14.5affected · semver
- before 1.15.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	k8s.io/ingress-nginx	before 0.0.0-20260319175635-5183b7d86137	0.0.0-20260319175635-5183b7d86137

Same product

kubernetes: all records

Other highest-scoring records for the same primary product.

CVE-2018-1002104Versions < 1.5 of the Kubernetes ingress default backend, which handles invalid ingress traffic, exposed prometheus metrics publicly.
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Kubernetes ingress-nginx	1.13.9	Vendor (CNA)
Kubernetes ingress-nginx	1.14.5	Vendor (CNA)
Kubernetes ingress-nginx	1.15.1	Vendor (CNA)
Go:k8s.io/ingress-nginx	0.0.0-20260319175635-5183b7d86137	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:2	2026-03-20

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMar 19, 2026
First PoCMar 20, 2026same day
TodayOct 22, 2026+217 d

EPSS, last 120 days-1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

wooseokdotkimfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope