CVE-2026-55723

NGINX Ingress Controller vulnerability

Published Jul 15, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The NGINX Ingress Controller builds its configuration from data provided in Custom Resource Definitions or Ingress annotations. Because this data is inserted into the generated NGINX configuration without sanitization, a malicious input can inject extra NGINX directives. This does not affect the data plane directly, but the attacker can create or delete files, disable services, or otherwise manipulate the control plane configuration.

Affected Systems

The vulnerability applies to the F5 NGINX Ingress Controller. Any deployed instance that allows creation or modification of CRDs or Ingress annotations is susceptible; specific version information is not supplied.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity, while the EPSS score of less than 1% suggests that, at present, the likelihood of exploitation is low. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires an authenticated attacker with sufficient RBAC permissions to modify CRDs or annotations via the Kubernetes API, making the likely vector the control‑plane API.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest F5 NGINX Ingress Controller patch or upgrade to a version that removes the unsanitized configuration generation.
  • Restrict RBAC so that only trusted accounts have rights to create or modify CRDs and Ingress annotations, enforcing least privilege.
  • Audit existing CRDs and Ingress annotations for unexpected or malicious directives and reject changes that contain disallowed configuration syntax.

Generated by OpenCVE AI on July 31, 2026 at 03:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared F5
F5 nginx Ingress Controller
Vendors & Products F5
F5 nginx Ingress Controller
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title NGINX Ingress Controller vulnerability
Weaknesses CWE-76
References
Metrics cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L'}

cvssV4_0

{'score': 8.7, 'vector': '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'}

Weaknesses
  • CWE-76

    Improper Neutralization of Equivalent Special Elements

Sources

Status
PUBLISHED
Assigner
f5
Published
Updated
Jul 16, 2026, 3:55 AM
Reserved
Jun 17, 2026, 11:45 PM
Status
Analyzed
Published
Jul 15, 2026, 3:16 PM
Modified
Oct 24, 2026, 9:10 PM