Skip to main content
VulnerabilityPublished Updated

CVE-2026-53873: picklescan · Incomplete List of Disallowed Inputs

Affects picklescanSource CVE Database V5

0
Compare

Public exploit available · CVSS 9.3 Critical : upgrade to 1.0.4 as a priority.

Data as of 8 Nov 2026, 14:19 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.09.3
CNA (VulnCheck)CVSS 3.19.8
CISA SSVC
Exploitation
Proof of concept is public or traded
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-06-17.

Patch
Available – fixed in 1.0.4
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

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 17 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulnCheck

    , 7 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 3 hours after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade picklescan to 1.0.4.

Affected software

ProductAffectedFixed in
picklescanpicklescanAffected
  • <1.0.4
Fixed in
  • 1.0.4
PyPIpicklescanpkg:pypi/picklescanOther threatsAffected
  • <1.0.4
Fixed in
  • 1.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…