CVE-2026-16760

waiting for further signalsZero needs more public information before it can validate it.

GHSA-cgc3-662q-qmrc ↗EUVD-2026-114513 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
trailofbits fickling <= 0.1.12
ETK-2026-3134Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/fickling
2h 52msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h02m
0
+2h
+6h
+8h
+10h
+12h

description

fickling releases through 0.1.12 can incorrectly approve malicious pickle data when assessing calls exposed through trusted standard-library modules. An attacker who can provide a pickle that an application passes to fickling.load() may cause code execution or file writes with the application's privileges.

mitigation

Do not use affected fickling versions as the sole safety gate for untrusted pickle data; reject untrusted pickles or process them in a strongly isolated environment. Apply a vendor release that removes this trust behavior when one is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 21:16Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-30 21:16Z
    ghsa: trigger signal, started the run
  2. 2026-10-30 21:16Z

this entry in the feed

GET /api/v1/feed/CVE-2026-16760

{
  "etk_id": "ETK-2026-3134",
  "cve_id": "CVE-2026-16760",
  "display_id": "CVE-2026-16760",
  "ghsa_id": "GHSA-cgc3-662q-qmrc",
  "euvd_id": "EUVD-2026-114513",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Pickle safety-check bypass in fickling",
  "summary": "fickling releases through 0.1.12 can incorrectly approve malicious pickle data when assessing calls exposed through trusted standard-library modules. An attacker who can provide a pickle that an application passes to fickling.load() may cause code execution or file writes with the application's privileges.",
  "mitigation": "Do not use affected fickling versions as the sole safety gate for untrusted pickle data; reject untrusted pickles or process them in a strongly isolated environment. Apply a vendor release that removes this trust behavior when one is available.",
  "vendor": "trailofbits",
  "product": "fickling",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.1.12"
      ],
      "ecosystem": "pypi",
      "fixed_versions": [],
      "package_name": "fickling",
      "purl": "pkg:pypi/fickling"
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.280524416666665,
  "t0_at": "2026-10-30T21:16:31.353000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-30T21:16:31.353000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T21:16:31.353000+00:00",
      "url": "https://github.com/advisories/GHSA-cgc3-662q-qmrc"
    }
  }
}

published 2026-10-31 00:56Z
last change 2026-10-31 02:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.