By vendor

Trailofbits vulnerabilities

Known CVEs affecting Trailofbits products, prioritized by severity, with SEC.co remediation and detection guidance.

2 published vulnerabilities

• CVE-2026-14534HIGH 8.8

  Fickling, a Python library designed to detect malicious pickle payloads before they execute, fails to block code execution via three standard library modules: _posixsubprocess, site, and atexit. An attacker can craft a specially formatted pickle file that exploits these blind spots, causing fickling's safety check to incorrectly report the payload as safe. When a developer uses fickling to load the pickle, the malicious code runs anyway. This is particularly dangerous because fickling is explicitly marketed as a security gate, so users trust its verdicts.

• CVE-2026-14535HIGH 8.8

  Trail of Bits fickling is a Python library designed to safely deserialize pickle files by analyzing them for dangerous imports before unpickling. A logic flaw in versions up to 0.1.11 breaks one of its two main safety checks. When fickling examines a pickle file, it runs two separate inspection passes: one flags obviously dangerous imports, and a second one (MLAllowlist) is supposed to catch sneaky imports from non-ML libraries that the first pass missed. However, the first pass leaves markers in shared memory that trick the second pass into skipping its checks entirely. As a result, any import from Python's standard library—except those on a small blocklist—gets a green light, even if it's dangerous. Because fickling's public API treats a green light as permission to actually deserialize and run the pickle, an attacker can craft a pickle file that imports and executes arbitrary standard library code, bypassing the security gate entirely.