CPython sandbox escape with no fix for security branches

What happened and what to do

The advisory, posted to the oss-sec list on November 5, 2026 by Alan Coopersmith, covers a sandbox escape in CPython, the reference interpreter for Python. According to the publication by Sybil, the issue could not be reported as a security vulnerability. Instead, a fix was submitted as a pull request to the CPython repository, and upstream has stated it will not backport that fix to security releases, leaving installations on those branches without the planned correction.

For a company, the practical point is not to treat Python's own sandbox as an isolation boundary for untrusted code, such as snippets generated by agents, third-party plugins or external inputs. An action plan can start by inventorying where CPython runs in production, which versions are in use and which services execute code or process external data. Those workloads can then be separated into containers or virtual machines with unprivileged users, restricted network access and a limited filesystem. It is also worth tracking the pull request and fix branches, setting up alerts for new publications on the topic, and defining a procedure to update or isolate quickly once a fix is released.

How the consultancy can help

Diagnosis of where CPython runs in the company and which workloads execute untrusted code, with an isolation plan using containers or VMs, a version inventory, monitoring of the upstream fix and an update procedure, implemented in the client's environment.

Next step

Send a short description of your Python environment, including versions in use, affected services and points where external code runs, and receive a scoped proposal for diagnosis and implementation.