CVE-2025-24514 | ingress-nginx controller - configuration injection via unsanitized auth-url annotation

Exp

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)

Published: 2025-03-25 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-24514 is rated High Exploit Risk (82.5/100): CVSS High severity, with high exploitation likelihood (EPSS 47.48%, 98th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2025-24514

EDB-ID Source Kind Published Link
52475 exploit_db edb 2026-02-04 Exploit-DB ↗

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

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-05-17 49.36% 47.48% -1.89%
2 2026-05-12 51.58% 49.36% -2.21%
3 2026-05-08 — 51.58% —

Full EPSS history (28 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H 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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2025-24514

GitHub Security Advisory for CVE-2025-24514

GHSA-fwwp-xcxw-39vq · Severity: high · Ecosystem: go — ingress-nginx controller - configuration injection via unsanitized auth-url annotation

OS Trackers for CVE-2025-24514

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2025-24514

Affected software / configurations for CVE-2025-24514

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-24514

cvelogic Threat Intelligence