CVE-2026-18313: rpcapd memory leak in libpcap before 1.10.7
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: The Tcpdump Group libpcap 1.10.7; azl3 libpcap 1.10.6-1 on Azure Linux 3.0 1.10.7-1.
Low priority for now. Upgrade to The Tcpdump Group libpcap 1.10.7; azl3 libpcap 1.10.6-1 on Azure Linux 3.0 1.10.7-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 5, 2026
- Updated
- Sep 8, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-401
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Tcpdump
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Tcpdump). Independent of NVD's CPE analysis and usually ahead of it.
The Tcpdump Group libpcap
- 1.9.xaffected
- 1.10.x and later · before 1.10.7affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libpcap | from 0 | — |
| Debian:14 | libpcap | before 1.10.7-1 | 1.10.7-1 |
| openSUSE:Leap 16.0 | libpcap | before 1.10.5-160000.5.1 | 1.10.5-160000.5.1 |
| openSUSE:Tumbleweed | libpcap | before 1.10.7-1.1 | 1.10.7-1.1 |
| SUSE:Linux Enterprise Micro 5.3 | libpcap | before 1.10.1-150400.3.12.1 | 1.10.1-150400.3.12.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP7 | libpcap | before 1.10.5-150700.3.13.1 | 1.10.5-150700.3.13.1 |
| SUSE:Linux Enterprise Server 15 SP6-LTSS | libpcap | before 1.10.4-150600.3.12.1 | 1.10.4-150600.3.12.1 |
| SUSE:Linux Micro 6.0 | libpcap | before 1.10.4-5.1 | 1.10.4-5.1 |
| SUSE:Linux Micro 6.1 | libpcap | before 1.10.4-slfo.1.1_3.1 | 1.10.4-slfo.1.1_3.1 |
| SUSE:Linux Micro 6.2 | libpcap | before 1.10.5-160000.5.1 | 1.10.5-160000.5.1 |
Same product
the tcpdump group: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-0799OOBR and OOBW in libpcap before 1.10.734Monitor
- CVE-2026-6554infinte loop in libpcap before 1.10.730Monitor
- CVE-2026-6244division by zero in libpcap before 1.10.722Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-11964Dec 30, 2025 · OOBW in utf_16le_to_utf_8_truncated() in libpcap7Monitor
- ← EarlierCVE-2026-18238Sep 5, 2026 · OOBR in rpcap client in libpcap before 1.10.720Monitor
- Later →CVE-2026-31911Sep 5, 2026 · abort() in libpcap before 1.10.7 on an invalid BPF opcode22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| The Tcpdump Group libpcap | 1.10.7 | Vendor (CNA) |
| azl3 libpcap 1.10.6-1 on Azure Linux 3.0 | 1.10.7-1 | Microsoft (MSRC) |
| debian:libpcap | 1.10.7-1 · Debian:14 | Package registry (OSV) |
| opensuse:libpcap | 1.10.7-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libpcap | 1.10.4-slfo.1.1_3.1 · SUSE:Linux Micro 6.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.