PatchTheCVEnginx ingress controller vulnerabilities and fixes
Recent CVEs affecting nginx ingress controller, with upgrade or downgrade steps. 3 tracked.
Also searched as: nginxingresscontroller.
nginx ingress controller has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-07-15. Highest priority: CVE-2026-55723 (score 45/100).
- CVE-2026-55723 HIGH 8.3 UPGRADE When NGINX Ingress Controller is configured with Custom Resource Definitions (CRDs) or Ingress annotations, an
- CVE-2026-52865 MEDIUM 6.5 UPGRADE When NGINX Ingress Controller processes Ingress or TransportServer resources, an authenticated, remote attacke
- CVE-2026-60065 LOW 3.7 UPGRADE UPGRADE When NGINX Plus is configured to use the Message Queuing Telemetry Transport (MQTT) filter module (ngx_stream_
FAQ
How do I fix nginx ingress controller vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is nginx ingress controller being exploited right now?
None of the tracked nginx ingress controller CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which nginx ingress controller CVE should I patch first?
CVE-2026-55723 currently ranks highest (45/100): When NGINX Ingress Controller is configured with Custom Resource Definitions (CRDs) or Ingress annotations, an.