CVE-2025-22153 | try/except* clauses could allow bypass RestrictedPython via type confusion bug in the CPython interpreter

RestrictedPython is a tool that helps to define a subset of the Python language which allows to provide a program input into a trusted environment. Via a type confusion bug in versions of the CPython interpreter starting in 3.11 and prior to 3.13.2 when using `try/except*`, RestrictedPython starting in version 6.0 and prior to version 8.0 could be bypassed. The issue is patched in version 8.0 of RestrictedPython by removing support for `try/except*` clauses. No known workarounds are available.

Published: 2025-01-23 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-22153 is rated Low Risk (36.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.05%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-22153

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-28 0.06% 0.05% -0.01%
2 2026-03-03 0.16% 0.06% -0.10%
3 2025-11-21 — 0.16% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-22153

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.9 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.3 6.0 [email protected]

Weakness enumeration for CVE-2025-22153

GitHub Security Advisory for CVE-2025-22153

GHSA-gmj9-h825-chq2 · Severity: high · Ecosystem: pip — try/except* clauses could allow bypass RestrictedPython via type confusion bug in the CPython interpreter

OS Trackers for CVE-2025-22153

vendor priority summary link
debian unimportant CVE-2025-22153 unimportant priority: Debian including 1 source packages (restrictedpython), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-22153
ubuntu medium CVE-2025-22153 medium priority: Ubuntu including 1 source packages (restrictedpython), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): not-affected 6, released 3. https://ubuntu.com/security/CVE-2025-22153

Affected software / configurations for CVE-2025-22153

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-22153

cvelogic Threat Intelligence