CVE-2026-87910

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 5 sources updated this week

Also known asEUVD-2026-76162 (ENISA EUVD) · GHSA-rj44-3777-mh5x (GitHub Security Advisories)Source: ENISA EUVD

5.7EG
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.6%CVSS: 5.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was ignored. Instead, the member should be skipped if either call returns None.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 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.6%
EPSS %ILE
49th
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.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 11, 2026

Last Modified

October 22, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github_pr.
Web page

tarfile hardlink fallback ignores custom extraction filter rejection via None · Issue #157265 · python/cpython · GitHub

https://github.com/python/cpython/issues/157265
GitHub pull request

gh-157265: Honor None result of filter for link fallbacks

Fix merged in python/cpython PR #157266 on 2026-09-11 — awaiting tagged release

https://github.com/python/cpython/pull/157266

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython3-12-main-3.12.14-1.2.hum12026-09-15redhat
redhatpython3-14-main-3.14.7-1.2.hum12026-09-15redhat
redhatpython3-10-main-3.10.21-1.2.hum12026-09-15redhat
redhatpython3-11-main-3.11.16-1.3.hum12026-09-15redhat
redhatpython3-13-main-3.13.15-1.2.hum12026-09-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 5 ecosystems)
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 8.0.0+dfsg-1 (13 versions)
  • every version on: no fix on record
—
python3.133.13.11-1 ... 3.13.9-1 (9 versions)
  • every version on: no fix on record
—
python3.143.14.0-1 ... 3.14.8-1 (30 versions)
  • every version on: no fix on record
—
python3.153.15.0~a8-1 ... 3.15.0~rc2-3 (12 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 8.0.0+dfsg-1 (13 versions)
  • every version on: no fix on record
—
python3.133.13.11-1 ... 3.13.9-1 (14 versions)
  • every version on: no fix on record
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—

Weakness Classification(2)

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

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 11× in last 7d / 69× 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 100 of 178 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. None are among the latest 100 rows. The 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-87910?
CVE-2026-87910 is a medium-severity vulnerability; its CVE record was published on September 11, 2026. When tarfile extracts a link on a system that doesn't support links, it falls back to extracting a member from the archive. In this case, the filter function is run twice: once for the extracted member, and once with name set to the location of the link. For one of the calls, the return value was…
When was the CVE record for CVE-2026-87910 published?
The CVE record for CVE-2026-87910 was published on September 11, 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 October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-87910 actively exploited?
CVE-2026-87910 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87910?
CVE-2026-87910 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87910?
A fix for CVE-2026-87910 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87910 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-87910

Explore →

Is Your Infrastructure Affected by CVE-2026-87910?

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