Cyber Resilience

CVE-2025-59303

Published
08 October 2025
Modified
15 April 2026
CVSS Score v3.1 6.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
EPSS Score 0.0024 16th percentile
Risk Priority 46 floored blend · peak EPSS

Summary

CVE-2025-59303 is a medium-severity Incomplete Filtering of Special Elements (CWE-791) vulnerability in Haproxy (inferred from references). Its CVSS base score is 6.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

Ingress Controller are 3.0.16-ee1, 1.11.13-ee1, and 1.9.15-ee1.

CWE(s)
CWE-791

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-39283Shared CWE-791
CVE-2026-44232Shared CWE-791
CVE-2025-0324Shared CWE-791
CVE-2024-47590Shared CWE-791
CVE-2024-45481Shared CWE-791
CVE-2023-31172Shared CWE-791
CVE-2025-2336Shared CWE-791
CVE-2025-0716Shared CWE-791
CVE-2024-32162Shared CWE-791
CVE-2024-8373Shared CWE-791

Affected Assets

Haproxy
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Input validation directly requires complete filtering of special elements on received data before further processing or forwarding.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require complete input filtering and sanitization to prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect incomplete filtering but does not itself implement the filtering.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle processes include validation activities that reduce the likelihood of CWE-791 but do not specify the control itself.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for input validation and sanitization that directly mitigates incomplete special-element filtering.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require defensive design patterns that prevent unfiltered data from reaching downstream components.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate complete filtering and escaping of special elements, directly eliminating CWE-791.

References