Quick answers
- Is CVE-2026-77180 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77180 being exploited in the wild.
- How severe is CVE-2026-77180?
- High severity, with a CVSS score of 8.3, published 2 September 2026.
- Which products and versions are affected?
- NGINX Ingress Controller.
- Is there a fix for CVE-2026-77180?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-77180 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-77180?
- Check whether you run NGINX Ingress Controller. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a configuration injection vulnerability in the NGINX Ingress Controller's configuration generator. Multiple user-controllable fields from Ingress annotations are written into the generated NGINX configuration file without proper sanitization. An authenticated attacker with permission to create or modify Ingress objects through the Kubernetes API can craft malicious annotation values that break out of their intended context and inject arbitrary NGINX directives. The attack requires valid Kubernetes API credentials and write access to Ingress resources; it does not affect the data plane or exposed services directly. Patches are expected to be available from the vendor.
Affected products
- NGINX Ingress Controller
Timeline
- 2026-09-02: disclosed