CVE-2025-24513 is a path traversal vulnerability in the Kubernetes ingress-nginx Admission Controller. According to the provided content, attacker-controlled data is incorporated into a filename by the Admission Controller feature, allowing directory traversal within the ingress-nginx container. The issue affects ingress-nginx versions prior to the March 24, 2025 fixes, and is described as an auth secret file path traversal flaw. The vulnerable behavior can be triggered through crafted Ingress-related input processed by the admission component, causing the controller to access unintended filesystem paths inside the container.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
One of a set of critical Ingress NGINX Controller vulnerabilities that can lead to unauthenticated remote code execution in Kubernetes environments.
A medium-severity path traversal vulnerability in ingress-nginx controller that could allow attackers with API server access and Ingress object permissions to leak sensitive information.
One of the ingress-nginx vulnerabilities patched in the March 2025 release; the article groups it among flaws involving nginx configuration handling that could contribute to Secret exposure and cluster takeover.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.