CVE-2025-11964 | OOBW in utf_16le_to_utf_8_truncated() in libpcap

On Windows only, if libpcap needs to convert a Windows error message to UTF-8 and the message includes characters that UTF-8 represents using 4 bytes, utf_16le_to_utf_8_truncated() can write data beyond the end of the provided buffer.

Published: 2025-12-31 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-11964 is rated Low Risk (8/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

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-11964

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 2025-12-31 — 0.01% —

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
1.9 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 0.5 1.4 [email protected]

Weakness enumeration for CVE-2025-11964

OS Trackers for CVE-2025-11964

vendor priority summary link
alpine low CVE-2025-11964: 1 source package rows (libpcap); 7 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 0, open 7. https://security.alpinelinux.org/vuln/CVE-2025-11964
debian unimportant CVE-2025-11964 unimportant priority: Debian including 1 source packages (libpcap), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-11964
redhat low — https://access.redhat.com/security/cve/CVE-2025-11964
suse low CVE-2025-11964 severity low: SUSE including 4 source package names (libpcap, libpcap-devel, libpcap1, libpcap1-32bit), 73 product×package rows across 30 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (30 product lines)): Known Not Affected 73. https://www.suse.com/security/cve/CVE-2025-11964/
ubuntu medium CVE-2025-11964 medium priority: Ubuntu including 1 source packages (libpcap), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): not-affected 9. https://ubuntu.com/security/CVE-2025-11964

Affected software / configurations for CVE-2025-11964

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-11964

cvelogic Threat Intelligence