CVE-2026-53873

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-17. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

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

picklescan before 1.0.4 contains an incomplete blocklist for the profile module that fails to block the module-level profile.run() function, allowing attackers to achieve arbitrary code execution via exec(). Attackers can craft malicious pickle files calling profile.run(statement) to execute arbitrary Python code while picklescan reports zero security issues.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
—
EPSS
37.3%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jul 12, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

profile.run blocklist mismatch allows exec() bypass · Advisory · mmaitre314/picklescan · GitHub

https://github.com/mmaitre314/picklescan/security/advisories/GHSA-7wx9-6375-f5wh
generic

picklescan - Arbitrary Code Execution via profile.run() Blocklist Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/picklescan-arbitrary-code-execution-via-profile-run-blocklist-bypass

Vendor Advisories for CVE-2026-53873(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 rangeFixed inDependents
picklescan0.0.1 ... 1.0.3 (39 versions)1.0.4—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:31 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
Show 36 more
  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 02:31 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-01 15:07 UTCEPSS rescore
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 14:05 UTCEPSS rescore
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
  26. 2026-06-19 19:26 UTCEPSS rescore
  27. 2026-06-19 19:26 UTCEPSS rescore
  28. 2026-06-18 17:52 UTCEPSS rescore
  29. 2026-06-18 17:52 UTCEPSS rescore
  30. 2026-06-18 12:24 UTCGHSA enrichment
  31. 2026-06-18 08:41 UTCGHSA enrichment
  32. 2026-06-18 04:58 UTCGHSA enrichment
  33. 2026-06-18 01:16 UTCGHSA enrichment
  34. 2026-06-17 21:34 UTCGHSA enrichment
  35. 2026-06-17 17:52 UTCEG score recompute
  36. 2026-06-17 17:52 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53873?
CVE-2026-53873 is a critical vulnerability published on June 17, 2026. picklescan before 1.0.4 contains an incomplete blocklist for the profile module that fails to block the module-level profile.run() function, allowing attackers to achieve arbitrary code execution via exec(). Attackers can craft malicious pickle files calling profile.run(statement) to execute…
When was CVE-2026-53873 disclosed?
CVE-2026-53873 was first published in the National Vulnerability Database on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53873 actively exploited?
CVE-2026-53873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53873?
CVE-2026-53873 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-53873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53873, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53873

Explore →

Is Your Infrastructure Affected by CVE-2026-53873?

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

Start Free Scan →Browse All CVEs