← Back
CVE-2026-55830
high
CVSS 8.3
Vulnerability in RestrictedPython (CVE-2026-55830)
Summary
vulnerability in RestrictedPython (CVE-2026-55830). Confidential information can be exposed externally. Exploitable via ``_write_``. Mitigation: upgrade to `8.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55830** has been found in RestrictedPython.
Attackers can target a specific entry point like ``_write_`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.3/10.
What to do: upgrade RestrictedPython to **8.3** or later.
If unsure, ask your IT team or search "RestrictedPython CVE-2026-55830" on the vendor's site.
CVE-2026-55830 (RestrictedPython) — CWE-184 / CVSS v3 8.3
Attack vector: remote (network-reachable)
Attack surface: `_write_` / `_print_` / `_getattr_` / `evil`
Patched: `8.3` — apply immediately
Workaround: None other than upgrading.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-184) exists in RestrictedPython. Attackers reach the vulnerable code path via ``_write_`` without authentication.
📍 Affected scope
RestrictedPython — . Attack surface: `_write_` / `_print_` / `_getattr_` / `evil`.
🔥 Severity
Severity: High (CVSS 8.3/10). Confidential information can be exposed externally
🔧 How to fix
Update to **8.3**.
🛡️ Workaround
Workaround: None other than upgrading.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'RestrictedPython' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'RestrictedPython' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `RestrictedPython` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
None other than upgrading.パッチが適用されるまでの応急処置として、None other than upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade RestrictedPython to 8.3ステージング環境で 8.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
RestrictedPython
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.3"}]}]
References
- web https://github.com/zopefoundation/RestrictedPython/commit/3737596ec9f28c34a073cc845bd2f4c0a80cb671
- web https://github.com/zopefoundation/RestrictedPython/security/advisories/GHSA-ffg3-p8fm-mjx2
- web https://nvd.nist.gov/vuln/detail/CVE-2026-55830
- web https://github.com/advisories/GHSA-ffg3-p8fm-mjx2