CVE-2026-14534

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 4 sources updated this weekElevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

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.8(high)
EPSS
24.8%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 6, 2026

Advisory Details (4)

Auto-updated Jul 4, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

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_pr 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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 14× 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-07-07 06:25 UTCEG score recompute
  2. 2026-07-07 06:25 UTCGHSA enrichment
  3. 2026-07-06 17:28 UTCEG score recompute
  4. 2026-07-06 17:28 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 04:32 UTCEG score recompute
  7. 2026-07-06 04:31 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 15:36 UTCEG score recompute
  10. 2026-07-05 15:36 UTCGHSA enrichment
  11. 2026-07-05 02:41 UTCEG score recompute
  12. 2026-07-05 02:41 UTCGHSA enrichment
  13. 2026-07-04 13:47 UTCEG score recompute
  14. 2026-07-04 13:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14534?
CVE-2026-14534 is a high vulnerability 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 UNSAFEIMPORTS denylist (fickle.py). Because these modules are absent from the denylist, fickling's checksafety() function returns LIKELYSAFE with…
When was CVE-2026-14534 disclosed?
CVE-2026-14534 was first published in the National Vulnerability Database on July 4, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14534 actively exploited?
CVE-2026-14534 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14534?
CVE-2026-14534 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-14534?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14534, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs