high CVSS 7.8

CVE-2026-42311·Python vulnerability

Pillow is a Python imaging library. From version 10.3.0 to before version 12.2.0, processing a malicious PSD file could lead to memory corruption, potentially resulting in a crash or arbitrary code execution. This issue has been patched in version 12.2.0.

Severity
high
Software
Python
Fixed in
12.2.0
Published
2026-05-09

Affected versions

From: 10.3.0

Until: 12.2.0

Fixed in: 12.2.0

How to fix this CVE

Update Pillow (Python's imaging library) to version 12.2.0 or later to remediate a memory corruption vulnerability in PSD file processing. Systems running Pillow versions 10.3.0 through 12.1.x should prioritize this update immediately, as processing malicious PSD files could trigger crashes or code execution. Verify your applications do not auto-load untrusted PSD files without validation.

sudo dnf update python3-pillow

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed Pillow version with: python3 -c 'import PIL; print(PIL.__version__)'
  2. List all Python packages with: pip list | grep -i pillow or python3 -m pip list | grep -i pillow
  3. Search application logs for PSD file processing errors: grep -r 'PSD\|.psd' /var/log/ | grep -i 'error\|crash\|segfault'
  4. Verify the fix by running: python3 -c 'import PIL; print("Pillow version:", PIL.__version__)' and confirm version is 12.2.0 or higher

FAQ

What is CVE-2026-42311?

This vulnerability affects Pillow, a Python image processing library, where maliciously crafted PSD (Photoshop) files can trigger memory corruption when opened, potentially leading to application crashes or arbitrary code execution.

Is CVE-2026-42311 being actively exploited?

No, this vulnerability is not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available, though the high CVSS score warrants prompt patching.

What versions of Python are affected by CVE-2026-42311?

Pillow versions 10.3.0 through 12.1.x are vulnerable; the issue is independent of Python version but requires Pillow to be patched to version 12.2.0 or later.

How do I check if my server is vulnerable to CVE-2026-42311?

Run `python3 -c 'import PIL; print(PIL.__version__)'` and compare the version against 10.3.0–12.1.x; any version in that range indicates vulnerability, while 12.2.0+ indicates it is patched.

Does Defensia detect CVE-2026-42311?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Pillow is installed on a monitored server, CVE-2026-42311 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-2026-42311. Free for 1 server.

Get started free