Skip to content
CVE Tracker

trailofbits vulnerabilities

15 published CVEs name trailofbits among the affected products.

Published CVEs
15
Last 12 months
12
Critical
2
Known exploited
0

Critical 2High 11Medium 2Low 0Not scored 0

CVEs per yearBy the year they were published

  1. 20232
  2. 20253
  3. 202610

Newest CVEs

  • CVE-2026-118938

    Fickling check_safety() bypass: dotted __qualname__ in STACK_GLOBAL resolves a class-method attribute path that evades call analysis

    trailofbits · fickling

    High8.8
  • CVE-2026-16760

    Fickling check_safety() bypass: likely_safe_imports grants module-origin trust to unvalidated standard library callables

    trailofbits · fickling

    High8.8
  • CVE-2026-14535

    Fickling MLAllowlist analysis pass rendered inoperative by shared mutable state in AnalysisContext.shorten_code()

    trailofbits · fickling

    High8.8
  • CVE-2026-14534

    Fickling check_safety() bypass via unlisted standard library modules (_posixsubprocess, site, atexit)

    trailofbits · fickling

    High8.8
  • CVE-2026-33753

    Improper Certificate Validation in rfc3161-client

    trailofbits · rfc3161-client

    Medium6.2
  • CVE-2026-22612

    Fickling vulnerable to detection bypass due to "builtins" blindness

    trailofbits · fickling

    High8.9
  • CVE-2026-22609

    Fickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklist

    trailofbits · fickling

    High8.9
  • CVE-2026-22608

    Fickling vulnerable to use of ctypes and pydoc gadget chain to bypass detection

    trailofbits · fickling

    High8.9
  • CVE-2026-22607

    Fickling Blocklist Bypass: cProfile.run()

    trailofbits · fickling

    High8.9
  • CVE-2026-22606

    Fickling has a bypass via runpy.run_path() and runpy.run_module()

    trailofbits · fickling

    High8.9