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.
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.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EPSS
- 36.8%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jun 29, 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-f5whgeneric
picklescan - Arbitrary Code Execution via profile.run() Blocklist Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/picklescan-arbitrary-code-execution-via-profile-run-blocklist-bypassVendor 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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| picklescan | 0.0.1 ... 1.0.3 (39 versions) | 1.0.4 | — |
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 36.8% 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
Is Your Infrastructure Affected by CVE-2026-53873?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.