medium CVSS 6.5

CVE-2024-47532·Python vulnerability

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.

Severity
medium
Software
Python
Fixed in
7.3
Published
2024-09-30

Affected versions

Until: 7.3

Fixed in: 7.3

How to fix this CVE

RestrictedPython versions prior to 7.3 contain an information disclosure vulnerability where attackers can bypass access restrictions through AttributeError manipulation combined with the string module. Upgrade to RestrictedPython 7.3 or later to remediate this issue. If immediate patching is not possible, restrict or remove the string module from the restricted execution environment configuration.

sudo dnf update python3-restrictedpython

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check the installed RestrictedPython version by running: python3 -c "import RestrictedPython; print(RestrictedPython.__version__)"
  2. Step 2: Verify if the string module is accessible in your RestrictedPython configuration by checking utility_builtins in your application code: grep -r "utility_builtins" /path/to/app/ | grep -i string
  3. Step 3: Search application logs for AttributeError exceptions combined with string module access patterns: grep -i "AttributeError" /var/log/application.log | grep -i "string"
  4. Step 4: After upgrading, re-run the version check to confirm RestrictedPython is at version 7.3 or later: python3 -c "import RestrictedPython; print(RestrictedPython.__version__)"

FAQ

What is CVE-2024-47532?

CVE-2024-47532 is an information disclosure vulnerability in RestrictedPython that allows authenticated users to circumvent access controls and retrieve sensitive data through a combination of AttributeError exploitation and string module manipulation. The flaw undermines the sandboxing intended to safely execute untrusted Python code.

Is CVE-2024-47532 being actively exploited?

No, there is no evidence of active exploitation in the wild or a publicly available proof-of-concept exploit. However, the medium severity rating (CVSS 6.5) warrants prompt patching to prevent potential future attacks.

What versions of RestrictedPython are affected by CVE-2024-47532?

All versions of RestrictedPython prior to version 7.3 are vulnerable. Version 7.3 and later contain the necessary fixes.

How do I check if my server is vulnerable to CVE-2024-47532?

Run: python3 -c "import RestrictedPython; v = RestrictedPython.__version__; print('Vulnerable' if tuple(map(int, v.split('.')[:2])) < (7, 3) else 'Patched')" to determine your vulnerability status.

Does Defensia detect CVE-2024-47532?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If RestrictedPython is installed on a monitored server, CVE-2024-47532 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-47532. Free for 1 server.

Get started free