libpcap BPF interpreter calls abort() if it encounters a BPF instruction that has an invalid opcode. In particular uncommon use cases a crafted filter program can terminate the OS process.
CVE-2026-31911
Score 5.5 from GitHub Security Advisory published 2026-09-05. a secondary CVSS source baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity55% × 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, 2026commit a715bcdde830 (the-tcpdump-group/libpcap)
Fix landed in the-tcpdump-group/libpcap commit a715bcdde830 — awaiting tagged release
https://github.com/the-tcpdump-group/libpcap/commit/a715bcdde830299cba4171514385cb17ec19b6e9Vendor Advisories for CVE-2026-31911(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libpcap | — | 1.10.7-r0 | — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libpcap | — | 1.10.7-r0 | — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libpcap | — | 1.10.7-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libpcap | — | 1.10.7-r0 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libpcap | 1.10.3-1 ... 1.10.6-2 (13 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libpcap | 1.10.5-2, 1.10.6-1, 1.10.6-2 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libpcap | 1.10.5-2, 1.10.6-1, 1.10.6-2 | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 50× 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.
- 2026-09-19 06:13 UTCEG score recompute
- 2026-09-19 06:13 UTCVendor advisory
- 2026-09-19 06:13 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 05:27 UTCEG score recompute
- 2026-09-18 05:27 UTCVendor advisory
- 2026-09-18 05:27 UTCGHSA enrichment
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-17 04:42 UTCEG score recompute
- 2026-09-17 04:42 UTCVendor advisory
- 2026-09-17 04:42 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 03:56 UTCEG score recompute
- 2026-09-16 03:56 UTCVendor advisory
- 2026-09-16 03:56 UTCGHSA enrichment
- 2026-09-15 03:10 UTCVendor advisory
- 2026-09-15 03:10 UTCGHSA enrichment
- 2026-09-14 02:23 UTCEG score recompute
- 2026-09-14 02:23 UTCVendor advisory
- 2026-09-14 02:23 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 01:38 UTCVendor advisory
- 2026-09-13 01:38 UTCGHSA enrichment
Show 25 moreShow fewer
- 2026-09-12 00:53 UTCEG score recompute
- 2026-09-12 00:53 UTCVendor advisory
- 2026-09-12 00:53 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 00:07 UTCEG score recompute
- 2026-09-11 00:07 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-09 23:20 UTCEG score recompute
- 2026-09-09 23:20 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-08 19:54 UTCGHSA enrichment
- 2026-09-08 17:01 UTCEG score recompute
- 2026-09-08 17:01 UTCVendor advisory
- 2026-09-08 17:01 UTCGHSA enrichment
- 2026-09-08 16:06 UTCEG score recompute
- 2026-09-08 16:06 UTCVendor advisory
- 2026-09-08 16:05 UTCGHSA enrichment
- 2026-09-07 20:55 UTCGHSA enrichment
- 2026-09-06 20:10 UTCEG score recompute
- 2026-09-06 20:10 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 19:24 UTCEG score recompute
- 2026-09-05 18:56 UTCEG score recompute
- 2026-09-05 18:55 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-31911?
When was CVE-2026-31911 disclosed?
Is CVE-2026-31911 actively exploited?
What is the CVSS score of CVE-2026-31911?
How do I remediate CVE-2026-31911?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31911
Is Your Infrastructure Affected by CVE-2026-31911?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.