CVE-2026-55830 is a sandbox escape vulnerability in RestrictedPython versions earlier than 8.3. The protected-name validation performed by check_function_argument_names() covered regular, variadic, and keyword-only arguments, but omitted positional-only arguments. A restricted program could therefore declare a positional-only local parameter using a protected guard-hook name, shadowing hooks used for attribute access, item access, writes, or printing. This can bypass the access policy enforced by the application embedding RestrictedPython.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability tracked as CVE-2026-55830 affecting Debian Linux 12.0 and 13.0. The supplied CVSS v3 vector indicates network attack vector, low attack complexity, high privileges required, user interaction required, changed scope, and high confidentiality and integrity impact with low availability impact.
A RestrictedPython sandbox guard-bypass vulnerability caused by failure to validate protected positional-only parameter names. Attacker-controlled restricted code can shadow guard hooks such as `_getattr_`, `_getitem_`, `_write_`, and `_print_`, bypassing enforced policy. In unsafe embedding applications, the bypass may be chainable to remote code execution.
An access control bypass vulnerability in RestrictedPython where positional-only arguments can shadow protected guard hook names, potentially bypassing the embedding application's access policy.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.