PoC Monitor
← All CVEs
CVE-2026-77180published 2 Sep 2026 15:40 UTCData: JSON · API

F5 NGINX Ingress Controller

NGINX Ingress Controller vulnerability

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.7high · scored by CNA · CWE-76
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

F5 NGINX Ingress Controller
  • >= 5.0.0, < 5.6.0
  • >= 2026-lts-r1, < 2026-lts-r5

Fixed in 5.6.0, 2026-lts-r5

Mitigation

Upgrade NGINX Ingress Controller to 5.6.0 or 2026-lts-r5 or later.

Workaround

* Restrict Kubernetes Role-based Access Control (RBAC) create, update, and patch permissions on VirtualServer, VirtualServerRoute, Policy, DosProtectedResource, and Ingress resources to trusted cluster administrators only. * Deploy an admission policy (Kyverno, OPA Gatekeeper, or ValidatingAdmissionPolicy) that rejects resources containing special characters in user-controlled fields.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published2 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.