NGINX Ingress Controller vulnerability

Answer in brief

CVE-2026-77180 records a Unknown severity vulnerability in NGINX Ingress Controller vulnerability. The current sources do not mark it as known exploited. The current feed maps F5/NGINX Ingress Controller (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 2, 2026Updated Sep 2, 2026Source checked Sep 2, 2026First seen by HOL Sep 2, 2026Material review Sep 2, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps F5/NGINX Ingress Controller (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
F5/NGINX Ingress Controllergeneric	>=5.0.0 <5.6.0 \|\| >=2026-lts-r1 <2026-lts-r5	5.6.0, 2026-lts-r5

Recommended response

Check inventory. Check lockfiles and deployed manifests for F5/NGINX Ingress Controller.
Review the reported fix. Update F5/NGINX Ingress Controller to 5.6.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 2, 2026

Sources and claim methodology

Source referencemy.f5.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.