Loading story…
Kubernetes maintainers disclosed multiple vulnerabilities in ingress-nginx affecting versions < 1.13.7 and < 1.14.3, including NGINX configuration injection paths that can lead to arbitrary code execution in the ingress-nginx controller context and Secrets disclosure. CVE-2026-24512 allows injection via the Ingress rules.http.paths.path field, and CVE-2026-1580 allows injection via the nginx.ingress.kubernetes.io/auth-method annotation; both are rated CVSS 8.8 and are especially high impact in default deployments where the controller can read Secrets cluster-wide. Recommended mitigations include upgrading to v1.13.7, v1.14.3, or later, and (as a temporary control) using validating admission policies to reject risky constructs such as ImplementationSpecific path types or the auth-method annotation.
A separate ingress-nginx issue, CVE-2026-24514 (CVSS 6.5), affects the validating admission controller feature and enables denial of service by sending oversized requests that drive memory consumption, potentially killing the controller pod or exhausting node memory. Detection guidance includes monitoring for unusually large requests (multi-megabyte) to the admission controller and suspicious payloads in rules.http.paths.path or the nginx.ingress.kubernetes.io/auth-method annotation. One referenced item describing CVE-2025-67601 in the Rancher CLI (credential/TLS handling weakness involving --skip-verify) is a different product and vulnerability and is not part of the ingress-nginx disclosures.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
5 events from the most recent confirmed update back to the earliest known activity.
Kubernetes published a product advisory for CVE-2025-15566, another ingress-nginx nginx configuration injection flaw tied to auth-proxy-set-headers. This expanded the publicly disclosed set of ingress-nginx configuration injection issues.
Reporting on CVE-2026-24512 explained that authenticated attackers could inject malicious NGINX configuration through an Ingress resource, potentially achieving arbitrary code execution and accessing Secrets available to the ingress-nginx controller. The Kubernetes security response committee recommended upgrading to fixed releases 1.13.7, 1.14.3, or later, or temporarily blocking ImplementationSpecific path usage with a validating admission controller.
Kubernetes published a product advisory for CVE-2026-24514, describing a denial-of-service vulnerability in the ingress-nginx Admission Controller. The disclosure added a separate availability-impacting issue to the ingress-nginx vulnerability set.
Kubernetes published a product advisory for CVE-2026-24512 affecting ingress-nginx, where the rules.http.paths.path field can be abused for nginx configuration injection. Later reporting said this could lead to arbitrary code execution and access to Kubernetes Secrets readable by the controller.
Kubernetes published a product advisory for CVE-2026-1580, an ingress-nginx nginx configuration injection issue involving the auth-method feature. The advisory made the vulnerability publicly known.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
5 references tracked. Mallory keeps watching after this page renders.
github.com
Open sourcecybersecuritynews.com
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Kubernetes maintainers disclosed five critical vulnerabilities in **ingress-nginx**, including **`CVE-2025-1974`** with a **CVSS 9.8** rating, warning that attackers on the Pod network could abuse configuration injection in the Validating Admission Controller to take over clusters without credentials. The flaws also affect how ingress-nginx builds **NGINX** configuration from crafted Ingress objects, potentially exposing Secrets available to the controller and leading to full cluster compromise. Patched releases **`ingress-nginx v1.12.1`** and **`v1.11.5`** were issued, and operators were urged to upgrade immediately or temporarily disable the Validating Admission Controller until patching is complete. The disclosure adds to broader concerns about Kubernetes networking and multi-tenant isolation, highlighted by **`CVE-2021-25740`**, an unpatchable issue that lets users with permission to modify **Endpoint** or **EndpointSlice** objects redirect service traffic to unauthorized IP addresses. In shared ingress-controller or load-balancer deployments, that behavior can allow one tenant to steer traffic into another tenant’s workloads and bypass intended network boundaries. Security researchers and vendors said the combined risk is highest in clusters that rely on shared ingress infrastructure with broad Secret access, and recommended tightening EndpointSlice permissions, avoiding shared ingress designs in sensitive environments, and evaluating the **Gateway API** as a safer architecture.
Jun 29, 2026
Belgium's Centre for Cybersecurity warned organizations to patch **Kubernetes ingress-nginx** immediately after disclosure of an arbitrary code execution issue affecting the widely used NGINX Ingress Controller. The flaw, tracked as **`CVE-2026-3288`**, is a high-severity configuration injection vulnerability that lets an authenticated user with permission to create or modify Ingress resources inject arbitrary **nginx** directives through a crafted double quote in the Ingress path field, potentially leading to remote code execution and exposure of secrets accessible to the controller. Sysdig reported that **`CVE-2026-3288`** was fixed on March 9, 2026 and stemmed from an incomplete remediation of the related **`CVE-2026-24512`**. According to the company, sanitization had been added to one code path but omitted from another, while built-in validation relied on an incomplete blocklist that attackers could bypass with payloads such as `return` directives. Affected releases include ingress-nginx versions before **`v1.13.8`**, **`v1.14.4`**, and **`v1.15.0`**; defenders were urged to upgrade, tighten **RBAC** permissions for Ingress changes, and monitor Kubernetes audit logs for signs of exploitation.
Jun 29, 2026
F5 disclosed multiple high-severity vulnerabilities affecting **NGINX Open Source**, **NGINX Plus**, and related products, including a critical heap-based buffer overflow in `ngx_http_proxy_v2_module` and `ngx_http_grpc_module` tracked as **CVE-2026-42055**. The flaw can be triggered remotely without authentication when HTTP/2 proxying or `grpc_pass` is enabled, `ignore_invalid_headers` is set to `off`, and `large_client_header_buffers` exceeds 2 MB, allowing oversized headers to crash worker processes and potentially enable code execution if ASLR is bypassed. F5 also disclosed **CVE-2026-42530**, a critical use-after-free in the open-source `ngx_http_v3_module` that can be exploited through a crafted HTTP/3 QUIC session to reopen a QPACK encoder stream, again causing worker restarts and possible code execution. A separate issue, **CVE-2026-11311**, affects **NGINX Gateway Fabric** when **NGINX Plus** is used as the data plane, allowing authenticated users with permission to modify relevant CRDs to inject arbitrary NGINX directives through unsanitized values in `NginxProxy.serverTokens` and `AuthenticationFilter.extraAuthArgs`. F5's out-of-band advisory said the exposure spans a broad set of products, including **NGINX Ingress Controller**, **NGINX Instance Manager**, **NGINX App Protect WAF**, **NGINX App Protect DoS**, **F5 WAF for NGINX Instance Manager**, and **F5 DoS for NGINX**. Updated releases, including **nginx 1.31.2** and the stable branch **1.30.3**, were published to address the core NGINX flaws, and defenders were urged to patch affected versions or disable HTTP/3 QUIC where immediate updates are not possible.
Jun 29, 2026