# CVE-2025-59303: Information disclosure in HAProxy Kubernetes Ingress Controller

> Users with create/update permissions can obtain ingress token secrets via config snippets in HAProxy Kubernetes Ingress Controller.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-jf49-m4qc-cf6c

## What is CVE-2025-59303?

CVE-2025-59303 is a medium-severity vulnerability in HAProxy Kubernetes Ingress Controller, published on 8 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HAProxy Kubernetes Ingress Controller before 3.1.13, when the config-snippets feature flag is used, accepts config snippets from users with create/update permissions. This can result in obtaining an ingress token secret as a response. The fixed versions of HAProxy Enterprise Kubernetes Ingress Controller are 3.0.16-ee1, 1.11.13-ee1, and 1.9.15-ee1.

Weakness: CWE-791 (Incomplete Filtering of Special Elements)

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


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

No fix has been published for CVE-2025-59303 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59303 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59303 is a medium-severity vulnerability in HAProxy Kubernetes Ingress Controller, published on 8 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59303 in the wild and no public exploit code.

Affected product: HAProxy Kubernetes Ingress Controller. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-59303/ (Markdown: https://insights.sbomify.com/CVE-2025-59303/index.md)
```

## Sources

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

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