CVE-2026-18313

rpcapd memory leak in libpcap before 1.10.7

Published Sep 5, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.

Remediation

Vendor Solution

Upgrade to libpcap 1.10.7.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Tcpdump
Tcpdump libpcap
Vendors & Products Tcpdump
Tcpdump libpcap
Type Values Removed Values Added
Description rpcapd can allocate up to 65536 bytes per each RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ message received from the client, but it never frees the memory, so it leaks memory even under normal use. A malicious client can cause the server to leak memory substantially faster.
Title rpcapd memory leak in libpcap before 1.10.7
Weaknesses CWE-401
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
Tcpdump
Published
Updated
Sep 8, 2026, 3:16 PM
Reserved
Jul 29, 2026, 5:47 PM
Status
Awaiting Analysis
Published
Sep 5, 2026, 7:16 PM
Modified
Sep 8, 2026, 7:20 PM
Severity
Moderate
Public date
Sep 5, 2026, 6:51 PM