ZeroHour

CVE-2025-1098

mass

Config Injection via Ingress Annotations Enables RCE in ingress-nginx

CVSS 3.1
8.8 high
EPSS
83%p100
Published
()
Modified
AI analysis

CVE-2025-1098 is an input-validation flaw (CWE-20) in the Kubernetes ingress-nginx controller: the `mirror-target` and `mirror-host` Ingress annotations are not properly sanitized, allowing arbitrary NGINX configuration directives to be injected into the controller's generated configuration. An attacker who can create or modify Ingress resources in the cluster (low privileges, no user interaction required) crafts these annotation values, and the injected configuration is consumed by the controller's NGINX instance to execute arbitrary code in the context of the ingress-nginx controller. Successful exploitation also leads to disclosure of Secrets accessible to the controller; in a default installation the controller can read every Secret cluster-wide, enabling credential theft and potentially full cluster takeover. Any Kubernetes cluster running a vulnerable ingress-nginx controller is affected, and public research tied to the related 'IngressNightmare' disclosures found the component in roughly 40% of cloud environments. No public proof-of-concept or confirmed in-the-wild exploitation is known yet, but EPSS assigns this CVE an 83.5% probability of exploitation within 30 days (100th percentile), so rapid patching is warranted.

What to do: Upgrade all ingress-nginx controllers to the patched releases (v1.12.1 or v1.11.5 per the vendor advisory) and restart controller pods. As interim mitigations, restrict RBAC so only trusted principals can create or update Ingress objects or set the mirror-target/mirror-host annotations (e.g., via a ValidatingAdmissionPolicy), and limit the controller's Secret access below cluster-wide where possible. Also patch the related IngressNightmare CVEs disclosed alongside this one and review clusters for exposed admission webhooks.

Affected
Kubernetes (kubernetes/ingress-nginx project) ingress-nginx controllerall versions prior to the patched releases published with the vendor advisory (v1.12.1 / v1.11.5); exact affected version ranges not specified in the source dat
Estimated exposure
mass≈100,000+ Kubernetes clusters plausibly affected (ingress-nginx is the most widely used ingress controller, present in ~40% of cloud environments per public… — Public IngressNightmare research reported ingress-nginx in roughly 40% of cloud environments with only about 6,500 controllers exposed to the public internet, and exploitation additionally requires Ingress-creation/modification privileges…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `mirror-target` and `mirror-host` Ingress annotations can be used to inject arbitrary 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.)

Weakness
CWE-20
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

In the news