CVE-2026-18313

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-09-05. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 5, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 5, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit f9775af1a0ec (the-tcpdump-group/libpcap)

Fix landed in the-tcpdump-group/libpcap commit f9775af1a0ec — awaiting tagged release

https://github.com/the-tcpdump-group/libpcap/commit/f9775af1a0ec76db60c7213241e6b48f1be10ac7

Vendor Advisories for CVE-2026-18313(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libpcap1.10.3-1 ... 1.10.6-2 (13 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libpcap1.10.5-2, 1.10.6-1, 1.10.6-2——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libpcap1.10.5-2, 1.10.6-1, 1.10.6-2——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 02:56 UTCEG score recompute
  2. 2026-09-20 02:56 UTCVendor advisory
  3. 2026-09-20 02:56 UTCGHSA enrichment
  4. 2026-09-19 04:25 UTCEG score recompute
  5. 2026-09-19 04:25 UTCVendor advisory
  6. 2026-09-19 04:25 UTCGHSA enrichment
  7. 2026-09-18 19:27 UTCEPSS rescore
  8. 2026-09-18 05:57 UTCEG score recompute
  9. 2026-09-18 05:57 UTCVendor advisory
  10. 2026-09-18 05:57 UTCGHSA enrichment
  11. 2026-09-17 07:28 UTCEG score recompute
  12. 2026-09-17 07:28 UTCVendor advisory
  13. 2026-09-17 07:28 UTCGHSA enrichment
  14. 2026-09-16 14:07 UTCEPSS rescore
  15. 2026-09-16 08:59 UTCEG score recompute
  16. 2026-09-16 08:59 UTCVendor advisory
  17. 2026-09-16 08:59 UTCGHSA enrichment
  18. 2026-09-16 05:14 UTCEPSS rescore
  19. 2026-09-15 09:19 UTCEG score recompute
  20. 2026-09-15 09:19 UTCVendor advisory
  21. 2026-09-15 09:19 UTCGHSA enrichment
  22. 2026-09-14 10:50 UTCEG score recompute
  23. 2026-09-14 10:50 UTCVendor advisory
  24. 2026-09-14 10:50 UTCGHSA enrichment
  25. 2026-09-13 16:46 UTCEPSS rescore
Show 34 more
  1. 2026-09-13 12:21 UTCEG score recompute
  2. 2026-09-13 12:21 UTCVendor advisory
  3. 2026-09-13 12:21 UTCGHSA enrichment
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-12 13:52 UTCVendor advisory
  6. 2026-09-12 13:52 UTCGHSA enrichment
  7. 2026-09-11 15:23 UTCEG score recompute
  8. 2026-09-11 15:23 UTCVendor advisory
  9. 2026-09-11 15:23 UTCGHSA enrichment
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-11 09:36 UTCEPSS rescore
  12. 2026-09-10 16:54 UTCEG score recompute
  13. 2026-09-10 16:54 UTCGHSA enrichment
  14. 2026-09-10 09:34 UTCEPSS rescore
  15. 2026-09-09 18:25 UTCEG score recompute
  16. 2026-09-09 18:25 UTCVendor advisory
  17. 2026-09-09 18:25 UTCGHSA enrichment
  18. 2026-09-08 22:00 UTCEPSS rescore
  19. 2026-09-08 19:54 UTCGHSA enrichment
  20. 2026-09-08 17:00 UTCEG score recompute
  21. 2026-09-08 17:00 UTCVendor advisory
  22. 2026-09-08 17:00 UTCGHSA enrichment
  23. 2026-09-08 16:06 UTCEG score recompute
  24. 2026-09-08 16:06 UTCVendor advisory
  25. 2026-09-08 16:05 UTCGHSA enrichment
  26. 2026-09-07 16:24 UTCEG score recompute
  27. 2026-09-07 16:24 UTCGHSA enrichment
  28. 2026-09-07 16:01 UTCEPSS rescore
  29. 2026-09-06 17:54 UTCEG score recompute
  30. 2026-09-06 17:54 UTCGHSA enrichment
  31. 2026-09-06 13:47 UTCEPSS rescore
  32. 2026-09-05 19:24 UTCEG score recompute
  33. 2026-09-05 18:56 UTCEG score recompute
  34. 2026-09-05 18:55 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18313?
CVE-2026-18313 is a medium vulnerability published on September 5, 2026. rpcapd can allocate up to 65536 bytes per each RPCAPMSGUPDATEFILTERREQ or RPCAPMSGSTARTCAPREQ 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.
When was CVE-2026-18313 disclosed?
CVE-2026-18313 was first published in the National Vulnerability Database on September 5, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18313 actively exploited?
CVE-2026-18313 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-18313?
CVE-2026-18313 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-18313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18313, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18313

Explore →

Is Your Infrastructure Affected by CVE-2026-18313?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs