high CVSS 7.8

CVE-2025-67748·Python vulnerability

Fickling is a Python pickling decompiler and static analyzer. Versions prior to 0.1.6 had a bypass caused by `pty` missing from the block list of unsafe module imports. This led to unsafe pickles based on `pty.spawn()` being incorrectly flagged as `LIKELY_SAFE`, and was fixed in version 0.1.6. This impacted any user or system that used Fickling to vet pickle files for security issues.

Severity
high
Software
Python
Fixed in
0.1.6
Published
2025-12-16

Affected versions

Until: 0.1.6

Fixed in: 0.1.6

How to fix this CVE

Update Fickling to version 0.1.6 or later to resolve the module validation bypass. This vulnerability allowed attackers to craft pickle files that evaded security checks by exploiting a missing `pty` module in the unsafe imports blocklist. Organizations relying on Fickling for pickle file vetting should prioritize this update to restore proper detection of malicious serialized objects.

sudo dnf install -y python3-pip && pip3 install --upgrade fickling

Defensia detects this vulnerability

How to check if you are affected

  1. Check Fickling version: pip3 show fickling | grep Version
  2. Verify if Fickling is used in your environment: grep -r 'from fickling' /path/to/application --include='*.py' || grep -r 'import fickling' /path/to/application --include='*.py'
  3. Review application logs for pickle deserialization or validation events, particularly those involving `pty.spawn()` calls or subprocess execution triggered by serialized objects
  4. After upgrade, confirm the new version: pip3 show fickling | grep Version (should be 0.1.6 or higher)

FAQ

What is CVE-2025-67748?

CVE-2025-67748 is a security bypass in Fickling versions before 0.1.6 where the `pty` module was omitted from the unsafe module blocklist, allowing malicious pickle files using `pty.spawn()` to be incorrectly classified as safe during static analysis.

Is CVE-2025-67748 being actively exploited?

No, according to CISA's Known Exploited Vulnerabilities catalog, CVE-2025-67748 is not currently being actively exploited in the wild, and no public exploit code is available.

What versions of Python are affected by CVE-2025-67748?

The vulnerability affects Fickling library versions prior to 0.1.6, regardless of the underlying Python version. Any environment running Fickling < 0.1.6 for pickle security analysis is at risk.

How do I check if my server is vulnerable to CVE-2025-67748?

Run `pip3 show fickling` and check the Version field. If the version is below 0.1.6, your installation is vulnerable. If Fickling is not installed, you are not affected by this vulnerability.

Does Defensia detect CVE-2025-67748?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Fickling is installed on a monitored server, CVE-2025-67748 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-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-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-26030CVSS 9.9Semantic Kernel, Microsoft's semantic kernel Python SDK, has a remote code execution vulnerability in versions prior to 1.39.4, specifically within the `InMemoryVectorStore` filter functionality. The problem has been fixed in version `python-1.39.4`. Users should upgrade this version or higher. As a workaround, avoid using `InMemoryVectorStore` for production scenarios.

References

Track CVEs across your fleet automatically

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

Get started free