CVE-2026-31912

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreHIGH confidence

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

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

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

libpcap BPF interpreter detects neither reaching the end of the filter program buffer due to lack of a return instruction nor executing a jump instruction with an offset that translates to a pointer outside of the buffer. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading the OS process memory in the 32GiB around the buffer on 64-bit architectures and in the entire address space on 32-bit architectures.

CVSS v3
5.5
EG Score
5.5(high)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 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 d3f358d3cffb (the-tcpdump-group/libpcap)

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

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

Vendor Advisories for CVE-2026-31912(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 29× in last 7d / 51× 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-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-18 19:06 UTCVendor advisory
  4. 2026-09-18 19:06 UTCGHSA enrichment
  5. 2026-09-17 21:23 UTCEG score recompute
  6. 2026-09-17 21:23 UTCVendor advisory
  7. 2026-09-17 21:23 UTCGHSA enrichment
  8. 2026-09-17 19:30 UTCEPSS rescore
  9. 2026-09-16 23:40 UTCEG score recompute
  10. 2026-09-16 23:40 UTCVendor advisory
  11. 2026-09-16 23:40 UTCGHSA enrichment
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 01:57 UTCVendor advisory
  15. 2026-09-16 01:57 UTCGHSA enrichment
  16. 2026-09-15 04:14 UTCEG score recompute
  17. 2026-09-15 04:14 UTCVendor advisory
  18. 2026-09-15 04:14 UTCGHSA enrichment
  19. 2026-09-14 06:31 UTCEG score recompute
  20. 2026-09-14 06:31 UTCVendor advisory
  21. 2026-09-14 06:31 UTCGHSA enrichment
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-13 08:48 UTCEG score recompute
  24. 2026-09-13 08:48 UTCVendor advisory
  25. 2026-09-13 08:48 UTCGHSA enrichment
Show 26 more
  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-12 11:05 UTCEG score recompute
  3. 2026-09-12 11:05 UTCVendor advisory
  4. 2026-09-12 11:05 UTCGHSA enrichment
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 13:12 UTCEG score recompute
  7. 2026-09-11 13:12 UTCGHSA enrichment
  8. 2026-09-10 15:29 UTCEG score recompute
  9. 2026-09-10 15:29 UTCGHSA enrichment
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-09 17:37 UTCEG score recompute
  12. 2026-09-09 17:37 UTCVendor advisory
  13. 2026-09-09 17:37 UTCGHSA enrichment
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-08 19:55 UTCEG score recompute
  16. 2026-09-08 19:54 UTCGHSA enrichment
  17. 2026-09-08 12:41 UTCVendor advisory
  18. 2026-09-08 12:41 UTCGHSA enrichment
  19. 2026-09-07 14:52 UTCGHSA enrichment
  20. 2026-09-06 17:09 UTCEG score recompute
  21. 2026-09-06 17:09 UTCGHSA enrichment
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 19:24 UTCEG score recompute
  25. 2026-09-05 18:56 UTCEG score recompute
  26. 2026-09-05 18:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-31912?
CVE-2026-31912 is a medium vulnerability published on September 5, 2026. libpcap BPF interpreter detects neither reaching the end of the filter program buffer due to lack of a return instruction nor executing a jump instruction with an offset that translates to a pointer outside of the buffer. In particular uncommon use cases a crafted filter program can cause the…
When was CVE-2026-31912 disclosed?
CVE-2026-31912 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-31912 actively exploited?
CVE-2026-31912 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 99.1% of all scored CVEs.
What is the CVSS score of CVE-2026-31912?
CVE-2026-31912 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31912?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31912, 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-31912

Explore →

Is Your Infrastructure Affected by CVE-2026-31912?

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

Start Free Scan →Browse All CVEs