CVE-2026-77180: NGINX Ingress Controller vulnerability
F5 · NGINX Ingress Controller
Vendor fix available · Affected: F5 NGINX Ingress Controller · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 43% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- F5 · NGINX Ingress Controllerfrom 5.0.0 before 5.6.0; from 2026-lts-r1 before 2026-lts-r5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- F5
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-77180 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.