CVE-2026-0799

HIGHPre-NVD 8.78.7—
EchelonGraph scoreHIGH confidence

Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2026-09-05. a secondary CVSS source baseline 8.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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

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.

CVSS v3
8.7
EG Score
8.7(high)
EG Risk
39(Track)
EG Risk 39/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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
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 48e8960a7108 (the-tcpdump-group/libpcap)

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

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

Vendor Advisories for CVE-2026-0799(2)

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

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
libpcap—1.10.7-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
libpcap—1.10.7-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
libpcap—1.10.7-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
libpcap—1.10.7-r0—
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(3)

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

Data Freshness Timeline

(refreshed 36× in last 7d / 72× 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-19 17:42 UTCEG score recompute
  2. 2026-09-19 17:42 UTCVendor advisory
  3. 2026-09-19 17:42 UTCGHSA enrichment
  4. 2026-09-19 06:22 UTCEG score recompute
  5. 2026-09-19 06:22 UTCVendor advisory
  6. 2026-09-19 06:22 UTCGHSA enrichment
  7. 2026-09-18 19:27 UTCEPSS rescore
  8. 2026-09-18 19:02 UTCVendor advisory
  9. 2026-09-18 19:02 UTCGHSA enrichment
  10. 2026-09-18 07:42 UTCVendor advisory
  11. 2026-09-18 07:42 UTCGHSA enrichment
  12. 2026-09-17 20:22 UTCEG score recompute
  13. 2026-09-17 20:22 UTCVendor advisory
  14. 2026-09-17 20:22 UTCGHSA enrichment
  15. 2026-09-17 08:38 UTCVendor advisory
  16. 2026-09-17 08:38 UTCGHSA enrichment
  17. 2026-09-16 21:18 UTCEG score recompute
  18. 2026-09-16 21:18 UTCVendor advisory
  19. 2026-09-16 21:18 UTCGHSA enrichment
  20. 2026-09-16 09:42 UTCVendor advisory
  21. 2026-09-16 09:42 UTCGHSA enrichment
  22. 2026-09-15 22:22 UTCVendor advisory
  23. 2026-09-15 22:21 UTCGHSA enrichment
  24. 2026-09-15 10:59 UTCEG score recompute
  25. 2026-09-15 10:59 UTCVendor advisory
Show 47 more
  1. 2026-09-15 10:59 UTCGHSA enrichment
  2. 2026-09-14 23:31 UTCVendor advisory
  3. 2026-09-14 23:31 UTCGHSA enrichment
  4. 2026-09-14 12:08 UTCVendor advisory
  5. 2026-09-14 12:08 UTCGHSA enrichment
  6. 2026-09-14 00:48 UTCVendor advisory
  7. 2026-09-14 00:48 UTCGHSA enrichment
  8. 2026-09-13 13:28 UTCVendor advisory
  9. 2026-09-13 13:28 UTCGHSA enrichment
  10. 2026-09-13 02:08 UTCVendor advisory
  11. 2026-09-13 02:08 UTCGHSA enrichment
  12. 2026-09-12 14:48 UTCVendor advisory
  13. 2026-09-12 14:48 UTCGHSA enrichment
  14. 2026-09-12 03:28 UTCVendor advisory
  15. 2026-09-12 03:28 UTCGHSA enrichment
  16. 2026-09-11 16:08 UTCEG score recompute
  17. 2026-09-11 16:08 UTCVendor advisory
  18. 2026-09-11 16:08 UTCGHSA enrichment
  19. 2026-09-11 14:52 UTCEPSS rescore
  20. 2026-09-11 09:36 UTCEPSS rescore
  21. 2026-09-11 04:37 UTCGHSA enrichment
  22. 2026-09-10 17:17 UTCEG score recompute
  23. 2026-09-10 17:16 UTCGHSA enrichment
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-10 05:54 UTCGHSA enrichment
  26. 2026-09-09 18:34 UTCVendor advisory
  27. 2026-09-09 18:34 UTCGHSA enrichment
  28. 2026-09-09 07:14 UTCEG score recompute
  29. 2026-09-09 07:14 UTCGHSA enrichment
  30. 2026-09-08 22:00 UTCEPSS rescore
  31. 2026-09-08 19:54 UTCEG score recompute
  32. 2026-09-08 19:54 UTCGHSA enrichment
  33. 2026-09-08 16:16 UTCVendor advisory
  34. 2026-09-08 16:16 UTCGHSA enrichment
  35. 2026-09-08 04:06 UTCGHSA enrichment
  36. 2026-09-07 16:46 UTCEG score recompute
  37. 2026-09-07 16:46 UTCGHSA enrichment
  38. 2026-09-07 16:01 UTCEPSS rescore
  39. 2026-09-07 05:26 UTCGHSA enrichment
  40. 2026-09-06 18:05 UTCEG score recompute
  41. 2026-09-06 18:05 UTCGHSA enrichment
  42. 2026-09-06 13:47 UTCEPSS rescore
  43. 2026-09-06 06:44 UTCEG score recompute
  44. 2026-09-06 06:44 UTCGHSA enrichment
  45. 2026-09-05 19:24 UTCEG score recompute
  46. 2026-09-05 18:56 UTCEG score recompute
  47. 2026-09-05 18:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-0799?
CVE-2026-0799 is a high vulnerability published on September 5, 2026. 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…
When was CVE-2026-0799 disclosed?
CVE-2026-0799 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-0799 actively exploited?
CVE-2026-0799 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 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-0799?
CVE-2026-0799 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-0799?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0799, 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-0799

Explore →

Is Your Infrastructure Affected by CVE-2026-0799?

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

Start Free Scan →Browse All CVEs