PYSEC-2026-1874
Vulnerability from pysec - Published: 2026-07-07 14:34 - Updated: 2026-07-07 17:25Impact
Via a type confusion bug in the CPython interpreter when using try/except* RestrictedPython could be bypassed.
We believe this should be fixed upstream in Python itself until that we remove support for try/except* from RestrictedPython.
(It has been fixed for some Python versions.)
Patches
Patched in version 8.0 by removing support for try/except* clauses
Workarounds
There is no workaround.
References
none
| Name | purl | restrictedpython | pkg:pypi/restrictedpython |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "restrictedpython",
"purl": "pkg:pypi/restrictedpython"
},
"ranges": [
{
"events": [
{
"introduced": "6.0"
},
{
"fixed": "8.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"6.0",
"6.1",
"6.2",
"7.0",
"7.0a1.dev0",
"7.0a1.dev1",
"7.0a2.dev0",
"7.1",
"7.2",
"7.2a1.dev0",
"7.3",
"7.4"
]
}
],
"aliases": [
"CVE-2025-22153",
"GHSA-gmj9-h825-chq2"
],
"details": "### Impact\nVia a type confusion bug in the CPython interpreter when using `try/except*` RestrictedPython could be bypassed.\n\nWe believe this should be fixed upstream in Python itself until that we remove support for `try/except*` from RestrictedPython.\n(It has been fixed for some Python versions.)\n\n### Patches\nPatched in version 8.0 by removing support for `try/except*` clauses\n\n### Workarounds\nThere is no workaround.\n\n### References\nnone\n",
"id": "PYSEC-2026-1874",
"modified": "2026-07-07T17:25:17.745402Z",
"published": "2026-07-07T14:34:49.069993Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/zopefoundation/RestrictedPython/security/advisories/GHSA-gmj9-h825-chq2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-22153"
},
{
"type": "WEB",
"url": "https://github.com/zopefoundation/RestrictedPython/commit/48a92c5bb617a647cffd0dadd4d5cfe626bcdb2f"
},
{
"type": "PACKAGE",
"url": "https://github.com/zopefoundation/RestrictedPython"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/restrictedpython"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-gmj9-h825-chq2"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "try/except* clauses could allow bypass RestrictedPython via type confusion bug in the CPython interpreter"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.