cve.bz

CVE-2026-55723 f5 nginx ingress controller

8.7 highEPSS 0.5%

High (8.7) in f5 nginx ingress controller. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
When NGINX Ingress Controller is configured with Custom Resource Definitions (CRDs) or 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 CRDs or annotations may craft values that inject arbitrary NGINX configuration directives. Impact: An authenticated attacker granted write access to NGINX Ingress Controller CRDs or 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.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

8.3 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-07-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-76 Improper Neutralization of Equivalent Special Elements
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-55723 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55723?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55723?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55723 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-55723

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-55723](https://cve.bz/cve/badge/CVE-2026-55723.svg)](https://cve.bz/cve/CVE-2026-55723)

HTML:

<a href="https://cve.bz/cve/CVE-2026-55723"><img src="https://cve.bz/cve/badge/CVE-2026-55723.svg" alt="CVE-2026-55723"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
F5 NGINX Ingress Controllerfrom 5.0.0 before 5.5.2
F5 NGINX Ingress Controllerfrom 2026-lts-r1 before 2026-lts-r3

References

Check your stackJSON