Skip to main content

NGINX Ingress Controller CVE-2026-52865

| EUVDEUVD-2026-44681 HIGH
NULL Pointer Dereference (CWE-476)
2026-07-15 f5 GHSA-gv6x-94m7-c6hh
7.1
CVSS 4.0 · Vendor: f5
Share

Severity by source

Vendor (f5) PRIMARY
7.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
6.5 MEDIUM

Network-reachable with low complexity and no interaction, but requires RBAC write privileges (PR:L); impact is an availability-only crash loop, so C:N/I:N/A:H with scope unchanged.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Primary rating from Vendor (f5).

CVSS VectorVendor: f5

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

4
Analysis Generated
Jul 15, 2026 - 15:31 vuln.today
Severity Changed
Jul 15, 2026 - 15:22 NVD
MEDIUM HIGH
CVSS changed
Jul 15, 2026 - 15:22 NVD
6.5 (MEDIUM) 7.1 (HIGH)
CVE Published
Jul 15, 2026 - 14:33 cve.org
HIGH 7.1

DescriptionCVE.org

When NGINX Ingress Controller processes Ingress or TransportServer resources, an authenticated, remote attacker with permission to create or modify Ingress or TransportServer resources can cause the NGINX Ingress Controller process to terminate.

Impact: The NGINX Ingress Controller control plane process terminates and enters a persistent crash loop while the malformed Ingress or TransportServer resource remains in the cluster. This vulnerability allows a remote, authenticated attacker with at least Ingress or TransportServer resource write access to cause a denial-of-service (DoS) on the NGINX Ingress Controller system. 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.

AnalysisAI

Denial of service in F5 NGINX Ingress Controller allows an authenticated remote attacker holding write access to Ingress or TransportServer resources to crash the control plane by submitting a malformed resource. Because the offending resource persists in the cluster, the controller re-reads it and re-crashes, producing a durable crash loop rather than a one-time outage. There is no public exploit identified at time of analysis, and impact is confined to the control plane with no data plane or confidentiality/integrity exposure.

Technical ContextAI

The affected component is the control plane of F5's NGINX Ingress Controller (CPE cpe:2.3:a:f5:nginx_ingress_controller), the Kubernetes controller that watches Ingress and TransportServer custom resources and translates them into NGINX configuration. The root cause is classified as CWE-476 (NULL Pointer Dereference): when the controller parses an attacker-supplied Ingress or TransportServer object, a code path dereferences a null pointer and the process aborts. Because the controller reconciles cluster state on a loop, the persisted malformed resource is repeatedly re-processed, converting a single crash into a persistent crash loop until the resource is manually removed. Note this is F5's commercial NGINX Ingress Controller, which is distinct from the separate community 'ingress-nginx' project.

RemediationAI

Patch available per vendor advisory - upgrade F5 NGINX Ingress Controller to the fixed release listed in F5 article K000161834 (https://my.f5.com/manage/s/article/K000161834); the exact fixed version is not enumerated in the provided data and must be taken from that advisory. As compensating controls until patching, tighten Kubernetes RBAC so that only trusted operators hold create/update permissions on Ingress and TransportServer resources, removing that access from untrusted or multi-tenant service accounts (trade-off: tenants lose self-service ingress configuration). Deploy a validating admission webhook or policy engine such as OPA/Gatekeeper or Kyverno to reject malformed Ingress/TransportServer specs before they persist, preventing the crash loop from being seeded (trade-off: added admission-path latency and policy maintenance). If a crash loop is already occurring, delete the offending malformed resource from the cluster to break the loop and restore the control plane.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise High Performance Computing 15 SP7 Affected
SUSE Linux Enterprise Module for Server Applications 15 SP7 Affected
SUSE Linux Enterprise Server 15 SP7 Affected
SUSE Linux Enterprise Server 16.1 Affected
SUSE Linux Enterprise Server for SAP Applications 15 SP7 Affected

Share

CVE-2026-52865 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy