CVE-2025-59303
BaseFortify
Publication date: 2025-10-08
Last updated on: 2025-10-08
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| haproxy | haproxy_kubernetes_ingress_controller | 1.11.13-ee1 |
| haproxy | haproxy_kubernetes_ingress_controller | 3.1.13 |
| haproxy | haproxy_kubernetes_ingress_controller | 1.9.15-ee1 |
| haproxy | haproxy_kubernetes_ingress_controller | 3.0.16-ee1 |
| haproxy | haproxy_kubernetes_ingress_controller | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-791 | The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in HAProxy Kubernetes Ingress Controller versions before 3.1.13 when the config-snippets feature flag is enabled. It allows users with create or update permissions to submit configuration snippets that can lead to obtaining an ingress token secret as a response.
How can this vulnerability impact me? :
An attacker with create or update permissions can exploit this vulnerability to obtain an ingress token secret, potentially allowing unauthorized access or control over ingress resources, which can lead to information disclosure and compromise of the Kubernetes environment.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade the HAProxy Kubernetes Ingress Controller to one of the fixed versions: 3.0.16-ee1, 1.11.13-ee1, or 1.9.15-ee1. Additionally, review and restrict permissions related to the config-snippets feature flag to prevent unauthorized users with create/update permissions from injecting config snippets.