Skip to content
Noroxi
CVE-2026-0799· NVD / CVE Program· CNA Tcpdump

OOBR and OOBW in libpcap before 1.10.7

Noroxi assessment

Priority: Monitor (action score 34/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.10% (FIRST EPSS).
  • Someone with local access to the system 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

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

Follow it and we'll tell you in the daily email digest when the record enters KEV, gets exploit code, is updated (including a fix) or its EPSS rises 20 points in a week. Connect a webhook and KEV listings and weaponized exploits arrive instantly.

Follow CVE-2026-0799

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? RSS feed for the tcpdump group records

Is your version affected? Check it

In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.

HighCVSS 8.7 · v3.1—No exploit Fix available
Published
Sep 5, 2026
Updated
Sep 8, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Tcpdump
8.7
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.

Noroxi 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 help

Affected 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

    • before 1.10.7affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10libpcapbefore 14:1.10.4-7.el10_2.114:1.10.4-7.el10_2.1
AlmaLinux:10libpcap-develbefore 14:1.10.4-7.el10_2.114:1.10.4-7.el10_2.1
AlmaLinux:8libpcapbefore 14:1.9.1-6.el8_1014:1.9.1-6.el8_10
AlmaLinux:8libpcap-develbefore 14:1.9.1-6.el8_1014:1.9.1-6.el8_10
AlmaLinux:9libpcapbefore 14:1.10.0-4.el9_8.114:1.10.0-4.el9_8.1
AlmaLinux:9libpcap-develbefore 14:1.10.0-4.el9_8.114:1.10.0-4.el9_8.1
Alpine:v3.21libpcapbefore 1.10.7-r01.10.7-r0
Debian:12libpcapall versions—
Debian:14libpcapbefore 1.10.7-11.10.7-1
openSUSE:Leap 16.0libpcapbefore 1.10.5-160000.5.11.10.5-160000.5.1
openSUSE:Tumbleweedlibpcapbefore 1.10.7-1.11.10.7-1.1
Red Hat:enterprise_linux:10.2libpcapbefore 14:1.10.4-7.el10_2.114:1.10.4-7.el10_2.1
Red Hat:enterprise_linux:10.2libpcap-debuginfobefore 14:1.10.4-7.el10_2.114:1.10.4-7.el10_2.1
Red Hat:enterprise_linux:10.2libpcap-debugsourcebefore 14:1.10.4-7.el10_2.114:1.10.4-7.el10_2.1
Red Hat:enterprise_linux:10.2libpcap-develbefore 14:1.10.4-7.el10_2.114:1.10.4-7.el10_2.1
Red Hat:enterprise_linux:8::baseoslibpcapbefore 14:1.9.1-6.el8_1014:1.9.1-6.el8_10
Red Hat:enterprise_linux:8::baseoslibpcap-debuginfobefore 14:1.9.1-6.el8_1014:1.9.1-6.el8_10
Red Hat:enterprise_linux:8::baseoslibpcap-debugsourcebefore 14:1.9.1-6.el8_1014:1.9.1-6.el8_10
Red Hat:enterprise_linux:8::crblibpcap-develbefore 14:1.9.1-6.el8_1014:1.9.1-6.el8_10
Red Hat:enterprise_linux:9::baseoslibpcapbefore 14:1.10.0-4.el9_8.114:1.10.0-4.el9_8.1
Red Hat:enterprise_linux:9::baseoslibpcap-debuginfobefore 14:1.10.0-4.el9_8.114:1.10.0-4.el9_8.1
Red Hat:enterprise_linux:9::baseoslibpcap-debugsourcebefore 14:1.10.0-4.el9_8.114:1.10.0-4.el9_8.1
Red Hat:enterprise_linux:9::crblibpcap-develbefore 14:1.10.0-4.el9_8.114:1.10.0-4.el9_8.1
Rocky Linux:10libpcapbefore 4:1.10.4-7.el10_2.14:1.10.4-7.el10_2.1

+9

Other highest-scoring records for the same primary product.

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
The Tcpdump Group libpcap1.10.7Vendor (CNA)
azl3 libpcap 1.10.6-1 on Azure Linux 3.01.10.7-1Microsoft (MSRC)
azl3 nmap 7.95-4 on Azure Linux 3.0—Microsoft (MSRC)
almalinux:libpcap14:1.10.0-4.el9_8.1 · AlmaLinux:9Package registry (OSV)
almalinux:libpcap14:1.10.4-7.el10_2.1 · AlmaLinux:10Package registry (OSV)
almalinux:libpcap-devel14:1.10.0-4.el9_8.1 · AlmaLinux:9Package registry (OSV)
almalinux:libpcap-devel14:1.10.4-7.el10_2.1 · AlmaLinux:10Package registry (OSV)
alpine:libpcap1.10.7-r0 · Alpine:v3.21Package registry (OSV)
debian:libpcap1.10.7-1 · Debian:14Package registry (OSV)
opensuse:libpcap1.10.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:libpcap14:1.10.0-4.el9_8.1 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:libpcap-debuginfo14:1.10.0-4.el9_8.1 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:libpcap-debugsource14:1.10.0-4.el9_8.1 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:libpcap-devel14:1.10.0-4.el9_8.1 · Red Hat:enterprise_linux:9::crbPackage registry (OSV)
rocky linux:libpcap4:1.10.0-4.el9_8.1 · Rocky Linux:9Package registry (OSV)
suse:libpcap1.10.4-slfo.1.1_3.1 · SUSE:Linux Micro 6.1Package 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.

EPSS, last 120 days

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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system 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
low · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
Low
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H

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.

ATT&CK techniques

—

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.

All records