CVE-2026-31912

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-72016 (ENISA EUVD) · GHSA-5r9v-8527-q4jv (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Tcpdump Group) states them: "Upgrade to libpcap 1.10.7 and migrate from bpf_filter() to pcap_offline_filter()."

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.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 5, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 5, 2026
Patch available. 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 rangeFix by version rangeDependents
libpcap—
  • every version up to 1.10.7-r0: fixed in 1.10.7-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
libpcap—
  • every version up to 1.10.7-r0: fixed in 1.10.7-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libpcap—
  • every version up to 1.10.7-r0: fixed in 1.10.7-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libpcap—
  • every version up to 1.10.7-r0: fixed in 1.10.7-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libpcap1.10.3-1 ... 1.10.7-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libpcap1.10.5-2, 1.10.6-1, 1.10.6-2, 1.10.7-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libpcap1.10.5-2, 1.10.6-1, 1.10.6-2
  • every version up to 1.10.7-1: fixed in 1.10.7-1
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 54× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 153 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 54 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-30 22:25 UTCOSV refresh
  4. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-25 14:36 UTCEG score recompute
  9. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-23 03:48 UTCEG score recompute
  12. 2026-10-23 03:48 UTCVendor advisory
  13. 2026-10-23 03:48 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  14. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-18 03:48 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-10-12 16:14 UTCEG score recompute
  23. 2026-10-11 19:57 UTCEG score recompute
  24. 2026-10-11 17:10 UTCEG score recompute
  25. 2026-10-11 14:38 UTCEG score recompute
Show 74 more
  1. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-09 22:55 UTCEG score recompute
  4. 2026-10-09 22:55 UTCVendor advisory
  5. 2026-10-09 22:55 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-09 01:01 UTCEG score recompute
  8. 2026-10-09 01:01 UTCVendor advisory
  9. 2026-10-09 01:01 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  12. 2026-10-07 22:53 UTCEG score recompute
  13. 2026-10-07 22:53 UTCVendor advisory
  14. 2026-10-07 22:53 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  16. 2026-10-06 14:41 UTCEG score recompute
  17. 2026-10-06 14:41 UTCVendor advisory
  18. 2026-10-06 14:41 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  19. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  20. 2026-10-05 16:38 UTCEG score recompute
  21. 2026-10-05 16:38 UTCVendor advisory
  22. 2026-10-05 16:38 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  24. 2026-10-04 18:06 UTCVendor advisory
  25. 2026-10-04 18:06 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  26. 2026-10-03 19:13 UTCEG score recompute
  27. 2026-10-03 19:13 UTCVendor advisory
  28. 2026-10-03 19:13 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  29. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  30. 2026-10-02 20:53 UTCEG score recompute
  31. 2026-10-02 20:53 UTCVendor advisory
  32. 2026-10-02 20:53 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  33. 2026-10-01 22:38 UTCEG score recompute
  34. 2026-10-01 22:38 UTCVendor advisory
  35. 2026-10-01 22:37 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  36. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  37. 2026-10-01 00:53 UTCEG score recompute
  38. 2026-10-01 00:53 UTCVendor advisory
  39. 2026-10-01 00:53 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  40. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · below the 1st percentile
  41. 2026-09-30 02:37 UTCEG score recompute
  42. 2026-09-30 02:37 UTCVendor advisory
  43. 2026-09-30 02:37 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  44. 2026-09-28 20:37 UTCVendor advisory
  45. 2026-09-28 20:37 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  46. 2026-09-27 21:36 UTCEG score recompute
  47. 2026-09-27 21:36 UTCVendor advisory
  48. 2026-09-27 21:36 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  49. 2026-09-26 23:54 UTCEG score recompute
  50. 2026-09-26 23:54 UTCVendor advisory
  51. 2026-09-26 23:53 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  52. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-09-26 01:42 UTCEG score recompute
  54. 2026-09-26 01:42 UTCVendor advisory
  55. 2026-09-26 01:42 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  56. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-09-25 03:12 UTCEG score recompute
  58. 2026-09-25 03:12 UTCVendor advisory
  59. 2026-09-25 03:12 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  60. 2026-09-24 05:24 UTCEG score recompute
  61. 2026-09-24 05:24 UTCVendor advisory
  62. 2026-09-24 05:24 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  63. 2026-09-23 07:41 UTCEG score recompute
  64. 2026-09-23 07:41 UTCVendor advisory
  65. 2026-09-23 07:41 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  66. 2026-09-22 09:58 UTCEG score recompute
  67. 2026-09-22 09:58 UTCVendor advisory
  68. 2026-09-22 09:58 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  69. 2026-09-21 12:15 UTCEG score recompute
  70. 2026-09-21 12:15 UTCVendor advisory
  71. 2026-09-21 12:15 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5
  72. 2026-09-20 20:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  73. 2026-09-20 14:32 UTCVendor advisory
  74. 2026-09-20 14:32 UTCGHSA enrichmentGHSA-5r9v-8527-q4jv · GitHub CVSS 5.5

Frequently asked(5)

What is CVE-2026-31912?
CVE-2026-31912 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-31912 published?
The CVE record for CVE-2026-31912 was published on September 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-31912 actively exploited?
CVE-2026-31912 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31912?
CVE-2026-31912 has a CVSS base score of 5.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-31912?
A fix for CVE-2026-31912 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Tcpdump Group) states them: "Upgrade to libpcap 1.10.7 and migrate from bpf_filter() to pcap_offline_filter()." The vendor advisories EchelonGraph has for CVE-2026-31912 are linked in the Vendor Advisories panel on this page.

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.