CVE-2025-24513 | ingress-nginx controller - auth secret file path traversal vulnerability

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where attacker-provided data are included in a filename by the ingress-nginx Admission Controller feature, resulting in directory traversal within the container. This could result in denial of service, or when combined with other vulnerabilities, limited disclosure of Secret objects from the cluster.

Published: 2025-03-25 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-24513 is rated Low Risk (31.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.15%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-24513

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-11 0.14% 0.15% +0.01%
2 2026-05-27 0.15% 0.14% -0.02%
3 2026-05-02 0.15%

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-24513

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
2.2 2.5 [email protected]

Weakness enumeration for CVE-2025-24513

GitHub Security Advisory for CVE-2025-24513

GHSA-242m-6h72-7hgp · Severity: medium · Ecosystem: go — ingress-nginx controller - auth secret file path traversal vulnerability

OS Trackers for CVE-2025-24513

vendor priority summary link
redhat medium https://access.redhat.com/security/cve/CVE-2025-24513

Affected software / configurations for CVE-2025-24513

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-24513

cvelogic Threat Intelligence