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

> Attacker-controlled data in filenames causes directory traversal in the ingress-nginx admission controller, leading to denial of service or secret disclosure.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-242m-6h72-7hgp, GO-2025-3564, MINI-469j-wj87-7338, MINI-6jjx-9c2f-3gxr, MINI-7chp-54mx-9rc3, MINI-834c-3cx4-44hp, MINI-9v5f-5fx5-hvq8, MINI-j94x-86g9-gm22, MINI-r827-jf9v-ghjf, MINI-v7q2-8m35-pjjm, MINI-w55x-jvc9-cx9f, MINI-wpmh-5wr2-j6pc

## What is CVE-2025-24513?

CVE-2025-24513 is a medium-severity path traversal vulnerability in kubernetes ingress-nginx, published on 24 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-24513?

5 open source packages ship an affected version, including k8s.io/ingress-nginx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `k8s.io/ingress-nginx` | Go | All versions | None |
| `k8s.io/ingress-nginx` | Go | All versions | 1.11.5 |
| `k8s.io/ingress-nginx` | Go | All versions | 1.11.5 |
| `k8s.io/ingress-nginx` | Go | From 1.12.0-beta.0 | 1.12.1 |
| `k8s.io/ingress-nginx` | Go | From 1.12.0-beta.0 | 1.12.1 |

## How do I fix CVE-2025-24513?

Upgrade k8s.io/ingress-nginx to a fixed version for your release line: 1.11.5 or 1.12.1.

## Is CVE-2025-24513 being exploited?

There is no known exploitation of CVE-2025-24513 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24513 and fix it if it is affected.

What it is: CVE-2025-24513 is a medium-severity path traversal vulnerability in kubernetes ingress-nginx, published on 24 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24513 in the wild and no public exploit code.

Affected packages and fixed versions:
- k8s.io/ingress-nginx (Go): affected all versions; no fix listed
- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.11.5
- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.11.5
- k8s.io/ingress-nginx (Go): affected from 1.12.0-beta.0; fixed in 1.12.1
- k8s.io/ingress-nginx (Go): affected from 1.12.0-beta.0; fixed in 1.12.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24513/ (Markdown: https://insights.sbomify.com/CVE-2025-24513/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24513
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24513
- OSV: https://osv.dev/vulnerability/CVE-2025-24513

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24513/
Summaries are generated and may contain mistakes; the official description above is the record.