NGINX Ingress Controller vulnerability
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in NGINX Ingress Controller 2026-lts-r3 and NGINX Ingress Controller 5.5.2.
When NGINX Ingress Controller processes Ingress or TransportServer resources, an authenticated, remote attacker with permission to create or modify Ingress or TransportServer resources can cause the NGINX Ingress Controller process to terminate. Impact: The NGINX Ingress Controller control plane process terminates and enters a persistent crash loop while the malformed Ingress or TransportServer resource remains in the cluster. This vulnerability allows a remote, authenticated attacker with at least Ingress or TransportServer resource write access to cause a denial-of-service (DoS) on the NGINX Ingress Controller system. 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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| F5 | NGINX Ingress Controller | >=2026-lts-r1 <2026-lts-r3, >=5.0.0 <5.5.2 | 2026-lts-r3, 5.5.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in F5, strongest first
Embed
A live severity badge for an advisory, README or ticket