CyberSecBulletin
CVE-2026-77180NVD status: Awaiting Analysis

NGINX Ingress Controller: Improper Neutralization of Equivalent Special Elements

CVE-2026-77180 is a high-severity improper neutralization of equivalent special elements vulnerability in NGINX Ingress Controller from F5, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 5.6.0, 2026-lts-r5 as the first without the flaw, so updating NGINX Ingress Controller to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update NGINX Ingress Controller to 5.6.0 or 2026-lts-r5, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
F5NGINX Ingress Controller5.0.0 up to, but not including, 5.6.0; 2026-lts-r1 up to, but not including, 2026-lts-r55.6.0, 2026-lts-r5

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
LowPerformance or availability is reduced.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA (f5.com).

Scoring systemScoreSeverityScored by
CVSS 4.08.7HighCNA (f5.com)
CVSS 3.18.3HighCNA (f5.com)

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Neutralization of Equivalent Special Elements

The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.

How developers prevent this class of flaw

  • Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Utilize an appropriate mix of allowlist and denylist parsing to filter equivalent special element syntax from all input.

More Improper Neutralization of Equivalent Special Elements vulnerabilities (CWE-76)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in NGINX Ingress Controller

All NGINX Ingress Controller vulnerabilities

Recent Improper Neutralization of Equivalent Special Elements vulnerabilities

Spotted an error? Tell us.