Advisory Database
  • Advisories
  • Dependency Scanning
  1. pypi
  2. ›
  3. fickling
  4. ›
  5. CVE-2025-67748

CVE-2025-67748: Fickling has Code Injection vulnerability via pty.spawn()

December 15, 2025 (updated December 20, 2025)

An unsafe deserialization vulnerability in Fickling allows a crafted pickle file to bypass the “unused variable” heuristic, enabling arbitrary code execution. This bypass is achieved by adding a trivial operation to the pickle file that “uses” the otherwise unused variable left on the stack after a malicious operation, tricking the detection mechanism into classifying the file as safe.

References

  • github.com/advisories/GHSA-r7v6-mfhq-g3m2
  • github.com/trailofbits/fickling
  • github.com/trailofbits/fickling/pull/108
  • github.com/trailofbits/fickling/pull/187
  • github.com/trailofbits/fickling/security/advisories/GHSA-r7v6-mfhq-g3m2
  • nvd.nist.gov/vuln/detail/CVE-2025-67748

Code Behaviors & Features

Detect and mitigate CVE-2025-67748 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 0.1.6

Fixed versions

  • 0.1.6

Solution

Upgrade to version 0.1.6 or above.

Impact 7.8 HIGH

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Learn more about CVSS

Weakness

  • CWE-184: Incomplete List of Disallowed Inputs
  • CWE-502: Deserialization of Untrusted Data
  • CWE-94: Improper Control of Generation of Code ('Code Injection')

Source file

pypi/fickling/CVE-2025-67748.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 04 Feb 2026 00:34:49 +0000.