CVE-2026-53873

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100

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 computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

Published

June 17, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Oct 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 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 rangeFix by version rangeDependents
picklescan0.0.1 ... 1.0.3 (39 versions)
  • every version up to 1.0.4: fixed in 1.0.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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.

Showing the most recent 100 of 160 total refreshes for this CVE.

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

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 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 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53873?
CVE-2026-53873 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53873?
A fix for CVE-2026-53873 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53873 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-53873

Explore →

Is Your Infrastructure Affected by CVE-2026-53873?

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