How severe is CVE-2026-53873?

CVE-2026-53873 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-53873 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-53873?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-53873 have an EU (EUVD) identifier?

Yes. CVE-2026-53873 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-37739.

When was CVE-2026-53873 published?

CVE-2026-53873 was published on 2026-06-17.

CVE-2026-53873

CVE-2026-53873 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-184.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v4: 9.3
EPSS exploit prediction: 1% (51st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-37739
Weakness: CWE-184
Published: 2026-06-17
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2026-53873?: 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.
How severe is CVE-2026-53873?: CVE-2026-53873 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-53873 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (51st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-53873?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-53873 have an EU (EUVD) identifier?: Yes. CVE-2026-53873 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-37739.
When was CVE-2026-53873 published?: CVE-2026-53873 was published on 2026-06-17.

References

Other CWE-184 vulnerabilities

CVE-2026-87985 — Critical (CVSS 10.0): An arbitrary code execution vulnerability in Mistral Vibe allows an attacker to bypass command permission checks using…
CVE-2026-79696 — Critical (CVSS 10.0): A Code Injection vulnerability in adk web in Google Cloud Agent Development Kit (ADK) for Python versions 2.0.0 through…
CVE-2026-57138 — Critical (CVSS 9.9): PraisonAI is a multi-agent teams system. From 1.4.0 until 1.7.2, codeMode in…
CVE-2026-65083 — Critical (CVSS 9.9): NVIDIA OpenShell for Linux contains a vulnerability in its sandbox provisioning API, where an attacker could cause an…
CVE-2026-47392 — Critical (CVSS 9.9): PraisonAI is a multi-agent teams system. Prior to version 4.6.40 of PraisonAI, corresponding to version 1.6.40 of…
CVE-2026-28363 — Critical (CVSS 9.9): In OpenClaw before 2026.2.23, tools.exec.safeBins validation for sort could be bypassed via GNU long-option…

Browse all CWE-184 vulnerabilities →