libpcap is widely deployed in network capture tools (tcpdump, Wireshark) and on many systems; this bug enables arbitrary memory access and potential RCE across many apps.
CVE-2026-0799
libpcap BPF interpreter allows arbitrary process memory access via crafted filters
Is CVE-2026-0799 being exploited?
Not confirmed. CVE-2026-0799 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.11% probability of exploitation in the next 30 days.
How severe is CVE-2026-0799?
CVE-2026-0799 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-0799?
Yes. A fix has been recorded for CVE-2026-0799. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-0799 affect?
CVE-2026-0799 affects libpcap, tcpdump, Wireshark, Any libpcap-based packet-capture tools. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-0799?
Upgrade libpcap/tcpdump/Wireshark to patched versions and avoid loading untrusted BPF filters.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted BPF filters permit arbitrary read/write of process memory, causing crashes, info disclosure, or possible code execution in libpcap-based apps.
Immediate action required
- affected< 1.10.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.