Skip to main content
VulnerabilityPublished

CVE-2026-116472: Kubernetes ingress-nginx · Improper Input Validation

Affects Kubernetes ingress-nginxSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.7 Low : upgrade to 1.15.2-prime1 when convenient.

Data as of 5 Nov 2026, 20:18 UTC

CVSS 3.1 base score
2.7Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (kubernetes)CVSS 3.12.7
Patch
Available – fixed in 1.15.2-prime1
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Rancher Prime RKE2 ingress-nginx to 1.15.2-prime1.

Affected software

ProductAffectedFixed in
Kubernetesingress-nginxAffected
  • All versions
Fixed in–
SUSERancher Prime RKE2 ingress-nginxAffected
  • <1.15.2-prime1
Fixed in
  • 1.15.2-prime1

AI-suggested

A fix is available in ingress-nginx version 1.15.2-prime1. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are necessary as the issue is resolved by the official patch.

Description

CVE-2026-116472 is an improper input validation vulnerability in the Kubernetes ingress-nginx controller. A user with permission to create an Ingress resource can exploit a missing check on the mirror-target Ingress annotation to write to an unauthenticated configuration API within ingress-nginx. This can cause denial of service by corrupting the ingress-nginx data plane, dropping all traffic until the configuration is corrected or the controller restarted. While theoretically this could allow traffic redirection from other Ingresses, practical risk is negligible due to required privileged knowledge and existing capabilities.

References

Community reviews

Loading reviews…