Arbitrary directive injection via unsanitized annotations
Published Sep 2, 2026 · Updated Sep 3, 2026
Configuration injection in F5 NGINX Ingress Controller before 5.6.0 allows remote authenticated users to inject NGINX directives. The configuration generator writes multiple user-controlled Ingress annotation fields into rendered NGINX configuration without neutralizing equivalent special elements. Access requires Kubernetes API permission to write Ingress annotations; resulting directives can create or delete files or disable control-plane services, without data-plane exposure.
Summary
What happened
Configuration injection in F5 NGINX Ingress Controller before 5.6.0 allows remote authenticated users to inject NGINX directives. The configuration generator writes multiple user-controlled Ingress annotation fields into rendered NGINX configuration without neutralizing equivalent special elements. Access requires Kubernetes API permission to write Ingress annotations; resulting directives can create or delete files or disable control-plane services, without data-plane exposure.
The record
- CVE
- CVE-2026-77180
- Published
- Sep 2, 2026
- Updated
- Sep 3, 2026
- Vendor
- F5 Networks
- Product
- NGINX Ingress Controller
- Classifications
- CWE-76, T1489, T1485
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2026-lts-r1 <2026-lts-r5
- Affected versionversion=5.0.0 <5.6.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo