CVE-2025-32464

HAProxy 2.2 through 3.1.6, in certain uncommon configurations, has a sample_conv_regsub heap-based buffer overflow because of mishandling of the replacement of multiple short patterns with a longer one.

Published: 2025-04-09 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-32464 is rated Moderate Risk (56.6/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 2.11%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-32464

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 2.20% 2.11% -0.09%
2 2026-05-18 4.65% 2.20% -2.45%
3 2026-05-09 — 4.65% —

Full EPSS history (17 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-32464

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 4.0 [email protected]

Weakness enumeration for CVE-2025-32464

OS Trackers for CVE-2025-32464

vendor priority summary link
alpine medium CVE-2025-32464: 1 source package rows (haproxy); 33 state rows across 4 repos (3.19-main, 3.20-main, 3.21-main, edge-main); fixed 0, open 33. https://security.alpinelinux.org/vuln/CVE-2025-32464
debian not yet assigned CVE-2025-32464 not yet assigned priority: Debian including 1 source packages (haproxy), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-32464
redhat medium — https://access.redhat.com/security/cve/CVE-2025-32464
suse medium — https://www.suse.com/security/cve/CVE-2025-32464/
ubuntu medium CVE-2025-32464 medium priority: Ubuntu including 1 source packages (haproxy), 8 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, upstream, xenial): not-affected 4, released 4. https://ubuntu.com/security/CVE-2025-32464

Affected software / configurations for CVE-2025-32464

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-32464

cvelogic Threat Intelligence