CVE-2026-53873: critical vulnerability in picklescan
picklescan - Arbitrary Code Execution via profile.run() Blocklist Bypass
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.3epss 0.5%
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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
picklescan · picklescanRelated CVEs — picklescan
In the same product, most dangerous first.
CVE-2026-56315CRITICALpicklescan - Remote Code Execution via Unblocked Standard Library ModulesEPSS 1.1%CVE-2025-71323CRITICALpicklescan - Remote Code Execution via Unblocked ctypes ModuleEPSS 1.0%CVE-2025-71368HIGHpicklescan - Arbitrary Code Execution via Undetected doctest.debug_scriptEPSS 0.8%CVE-2025-71321CRITICALpicklescan - Arbitrary File Writing via distutils Module BypassEPSS 0.8%CVE-2026-3490CRITICALpicklescan - Universal Blocklist Bypass via pkgutil.resolve_nameEPSS 0.8%CVE-2025-71320CRITICALpicklescan - Remote Code Execution via Incomplete Disallowed InputsEPSS 0.8%