ZeroHour

CVE-2026-77180

large

Authenticated configuration injection in F5 NGINX Ingress Controller

CVSS 4.0
8.7 high
EPSS
<1%p23
Published
()
Modified
AI analysis

F5 NGINX Ingress Controller contains a configuration injection flaw (CWE-76) in its configuration generator: when Ingress resources carry annotations, multiple user-controllable fields are written into the generated NGINX configuration without sanitization. An attacker who is authenticated to the Kubernetes API and has permission to create or modify these Ingress annotations can craft values that inject arbitrary NGINX configuration directives, create or delete files, or disable services. The issue is control plane only, with no data plane exposure, and deployments that use Ingress annotations are the ones affected. All supported releases are potentially exposed; the available data does not specify affected version ranges, and versions that have reached End of Technical Support (EoTS) are not evaluated. Exploitation is not currently known: EPSS gives a 0.3% probability of exploitation in the next 30 days, the flaw is not in CISA KEV, and no public proof-of-concept exists.

What to do: Upgrade NGINX Ingress Controller to the patched release identified in F5's security advisory (specific fixed version is not provided in the available data) and avoid running EoTS versions. In the meantime, restrict Kubernetes RBAC permissions to create or modify Ingress objects and their annotations to trusted principals, and audit existing annotations for embedded NGINX directive syntax such as newlines, semicolons, or braces.

Affected
F5 NGINX Ingress Controller
Estimated exposure
largelikely tens of thousands of Kubernetes deployments (widely deployed ingress controller; exact install counts not in data) — NGINX Ingress Controller is among the commonly adopted Kubernetes ingress controllers, and many clusters grant non-admin users RBAC write access to Ingress objects, but no public install or internet-exposure counts are provided in the…

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

Description

When NGINX Ingress Controller is configured with Ingress annotations, an injection vulnerability exists in the configuration generator of NGINX Ingress Controller. Multiple user-controllable fields are written into the generated NGINX configuration without sanitization. An authenticated attacker with permission to create or modify these annotations may craft values that inject arbitrary NGINX configuration directives. Impact: An authenticated attacker granted write access to NGINX Ingress Controller Ingress annotations through the Kubernetes API may be able to inject arbitrary NGINX configuration directives, create or delete files, or disable services. There is no data plane exposure; this is a control plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness
CWE-76
Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

In the news

No ingested article mentions this CVE yet.