CVE-2025-11964: The Tcpdump Group libpcap · Out-of-bounds Write
Affects The Tcpdump Group libpcapSource CVE Database V5
Not known to be exploited · CVSS 1.9 Low.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 31 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubthe-tcpdump-group/libpcappkg:github/the-tcpdump-group/libpcapOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-11964, organizations should: 1) Monitor for and apply vendor patches or updates to libpcap as soon as they become available, ensuring the vulnerable function is corrected. 2) Audit and restrict local administrative privileges to minimize the risk of exploitation by unauthorized users. 3) Review and harden Windows error message handling in applications that utilize libpcap to avoid triggering the vulnerable code path. 4) Employ runtime memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) on Windows hosts to reduce exploitation success. 5) Conduct thorough testing of network monitoring and forensic tools after updates to verify stability and correctness. 6) Maintain robust logging and monitoring to detect anomalous behavior indicative of exploitation attempts. 7) Consider isolating critical network analysis systems to limit exposure to potential insider threats. These steps go beyond generic advice by focusing on privilege management, error handling, and proactive patch management tailored to the vulnerability's characteristics.
Description
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.