CVE-2026-14534

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-04. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-41675 (ENISA EUVD) · GHSA-v8cr-9jrc-fwf9 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Trail of Bits fickling versions up to and including 0.1.10 do not include the Python standard library modules _posixsubprocess, site, and atexit in the UNSAFE_IMPORTS denylist (fickle.py). Because these modules are absent from the denylist, fickling's check_safety() function returns LIKELY_SAFE with zero findings for pickle payloads that invoke dangerous functions including _posixsubprocess.fork_exec (C-level process spawner capable of executing arbitrary binaries), site.execsitecustomize (executes arbitrary site customization code), and atexit._run_exitfuncs (triggers all registered exit handler callbacks). The fickling.load() API chains check_safety() into pickle.loads() as an explicit security gate; a LIKELY_SAFE verdict causes the payload to be deserialized and executed. This shares the same root cause as CVE-2026-22607 (cProfile), CVE-2025-67748 (pty), and CVE-2025-67747 (marshal/types). OvertlyBadEvals does not flag these modules because they are standard library imports. UnsafeImports does not flag them because they are not in the denylist. The UnusedVariables heuristic is defeated by the SETITEMS opcode pattern.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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 low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

July 4, 2026

Last Modified

October 25, 2026

Advisory Details (4)

Auto-updated Jul 4, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Bypass of check_safety() via unlisted standard library modules (_posixsubprocess, site, atexit) · Advisory · trailofbits/fickling · GitHub

https://github.com/trailofbits/fickling/security/advisories/GHSA-m6fh-58r7-x697
GitHub release Patch Available

v0.1.11

Patch available: trailofbits/fickling v0.1.11

https://github.com/trailofbits/fickling/releases/tag/v0.1.11
GitHub pull request Patch Available

Expand UNSAFE_IMPORTS blocklist (GHSA-m6fh-58r7-x697)

Patch available: trailofbits/fickling v0.1.11 (PR #272 merged 2026-05-06)

https://github.com/trailofbits/fickling/pull/272
GitHub commit Patch Available

commit e8408615b63a (trailofbits/fickling)

Patch available: trailofbits/fickling v0.1.11 (contains commit e8408615b63a)

https://github.com/trailofbits/fickling/commit/e8408615b63adf034f891f653692ab9b51f0f5af

Vendor Advisories for CVE-2026-14534(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
fickling0.0.1 ... 0.1.9 (17 versions)
  • every version up to 0.1.11: fixed in 0.1.11
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 44× 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 257 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 157 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-14534?
CVE-2026-14534 is a high-severity vulnerability; its CVE record was published on July 4, 2026. Trail of Bits fickling versions up to and including 0.1.10 do not include the Python standard library modules _posixsubprocess, site, and atexit in the UNSAFE_IMPORTS denylist (fickle.py). Because these modules are absent from the denylist, fickling's check_safety() function returns LIKELY_SAFE…
When was CVE-2026-14534 made public?
CVE-2026-14534 was made public on June 28, 2026: that is the date its CVE record's CNA, Bombadil Systems LLC, gives for when the vulnerability was made public. The CVE record itself was published on July 4, 2026. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-14534 actively exploited?
CVE-2026-14534 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14534?
CVE-2026-14534 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14534?
A fix for CVE-2026-14534 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-14534 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-14534

Explore →

Is Your Infrastructure Affected by CVE-2026-14534?

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