CVE-2026-18313
published 2026-09-05CVE-2026-18313: 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…
PriorityP419medium4.3CVSS 3.1
AVNACLPRLUINSUCNINAL
EPSS
0.23%
12.7th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| openshift | ose-rhel-coreos-8 | — | — |
| openshift | ose-rhel-coreos-9 | — | — |
| the_tcpdump_group | libpcap | — | — |
| the_tcpdump_group | libpcap | — | — |
| the_tcpdump_group | libpcap | >= 1.10.x < 1.10.7 | 1.10.7 |
CVSS provenance
nvdv3.14.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
vendor_redhat4.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
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 norma
ghsa_unreviewed·2026-09-05
CVE-2026-18313 [MEDIUM] CWE-401 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 norma
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.
VulDB
Tcpdump Group libpcap up to 1.9.x/1.10.6 memory leak (EUVD-2026-72020)
vuldb·2026-09-05·CVSS 4.3
CVE-2026-18313 [MEDIUM] Tcpdump Group libpcap up to 1.9.x/1.10.6 memory leak (EUVD-2026-72020)
A vulnerability was found in Tcpdump Group libpcap up to 1.9.x/1.10.6. It has been declared as critical. Affected by this issue is some unknown functionality. Such manipulation leads to memory leak.
This vulnerability is documented as CVE-2026-18313. The attack can be executed remotely. There is not any exploit available.
It is recommended to upgrade the affected component.
Red Hat
libpcap: libpcap: Denial of Service via memory leak in rpcapd
vendor_redhat·2026-09-05·CVSS 4.3
CVE-2026-18313 [MEDIUM] CWE-772 libpcap: libpcap: Denial of Service via memory leak in rpcapd
libpcap: libpcap: Denial of Service via memory leak in rpcapd
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.
A flaw was found in libpcap, specifically within the rpcapd daemon. This vulnerability allows a remote attacker to cause a denial of service (DoS) by sending specially crafted RPCAP_MSG_UPDATEFILTER_REQ or RPCAP_MSG_STARTCAP_REQ messages. The rpcapd daemon allocates memory for these messages but fails to free it, leading to a memory leak. Over time, this can exhaust available memory, making the service unavailable.
Statement: This Moderate impact
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-18313 libpcap: libpcap: Denial of Service via memory leak in rpcapd [fedora-all]
bugzilla·2026-09-09·CVSS 4.3
CVE-2026-18313 [MEDIUM] CVE-2026-18313 libpcap: libpcap: Denial of Service via memory leak in rpcapd [fedora-all]
CVE-2026-18313 libpcap: libpcap: Denial of Service via memory leak in rpcapd [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
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.
Bugzilla
CVE-2026-18313 libpcap: libpcap: Denial of Service via memory leak in rpcapd
bugzilla·2026-09-05·CVSS 4.3
CVE-2026-18313 [MEDIUM] CVE-2026-18313 libpcap: libpcap: Denial of Service via memory leak in rpcapd
CVE-2026-18313 libpcap: libpcap: Denial of Service via memory leak in rpcapd
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.
2026-09-05
Published