p PatchFirst

PatchFirst · Latest vulnerabilities

restrictedpython vulnerabilities

Vulnerabilities published for restrictedpython in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 5

  1. CVE-2026-76825

    High · CVSS 8.4EPSS 0.62%No fix published

    RestrictedPython: Sandbox escape via string.Formatter field resolution

    RestrictedPython is a tool that helps define a subset of the Python language for accepting program input in a trusted environment. Prior to 8.4, RestrictedPython could allow a sandbox escape when a custom import policy or globals exposed the standard library string module, the string.Formatter class, a Formatter instance, or a Formatter subclass to restricted code. The string.Formatter methods format, get_field, get_value, and vformat performed attribute and item traversal internally without passing through RestrictedPython's safer_getattr protections. Restricted code could use those live object references to reach function globals, builtins,

    Published Updated
  2. CVE-2026-55830

    High · CVSS 8.3EPSS 0.29%No fix published

    RestrictedPython guard hooks can be shadowed via positional-only arguments

    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. Prior to 8.3, check_function_argument_names() rejected protected guard hook names for regular, variadic, and keyword-only arguments but omitted positional-only arguments, allowing __getattr__, _getitem_, _write_, or _print_ to be shadowed by a local parameter and bypass the embedding application's access policy. This issue is fixed in version 8.3.

    Published Updated
  3. CVE-2024-47532

    High · CVSS 8.7EPSS 0.72%No fix published

    RestrictedPython information leakage via `AttributeError.obj` and the `string` module

    RestrictedPython is a restricted execution environment for Python to run untrusted code. A user can gain access to protected (and potentially sensible) information indirectly via AttributeError.obj and the string module. The problem will be fixed in version 7.3. As a workaround, If the application does not require access to the module string, it can remove it from RestrictedPython.Utilities.utility_builtins or otherwise do not make it available in the restricted execution environment.

    Published Updated
  4. CVE-2023-41039

    High · CVSS 8.3EPSS 0.68%No fix published

    Sandbox escape via various forms of "format" in RestrictedPython

    RestrictedPython is a restricted execution environment for Python to run untrusted code. Python's "format" functionality allows someone controlling the format string to "read" all objects accessible through recursive attribute lookup and subscription from objects he can access. This can lead to critical information disclosure. With `RestrictedPython`, the format functionality is available via the `format` and `format_map` methods of `str` (and `unicode`) (accessed either via the class or its instances) and via `string.Formatter`. All known versions of `RestrictedPython` are vulnerable. This issue has been addressed in commit `4134aedcff1` whi

    Published Updated
  5. CVE-2023-37271

    High · CVSS 8.4EPSS 0.85%No fix published

    RestrictedPython vulnerable to arbitrary code execution via stack frame sandbox escape

    RestrictedPython is a tool that helps to define a subset of the Python language which allows users to provide a program input into a trusted environment. RestrictedPython does not check access to stack frames and their attributes. Stack frames are accessible within at least generators and generator expressions, which are allowed inside RestrictedPython. Prior to versions 6.1 and 5.3, an attacker with access to a RestrictedPython environment can write code that gets the current stack frame in a generator and then walk the stack all the way beyond the RestrictedPython invocation boundary, thus breaking out of the restricted sandbox and potentia

    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →