CVE-2026-118938

validatedZero produced an exploit or a check.

GHSA-6jfm-qx2v-27jg ↗EUVD-2026-114515 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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-3135Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/fickling
+4h13mTTV
13mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+4h13magent stopped
0
+1h
+2h
+3h

description

fickling through version 0.1.12 can incorrectly approve pickles containing dotted attribute references during safety analysis. An attacker who can supply a pickle that is subsequently loaded through the affected loading path can cause arbitrary code execution despite the safety check.

mitigation

Do not load untrusted pickles with fickling, including when its safety check reports that they are safe; reject them or process them in an isolated environment. No fixed version is identified in the evidence, so track for a release that explicitly corrects dotted attribute-path analysis before relying on this check.

check
available
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
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-30 21:19Z
Δ 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 check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3135",
  "cve_id": "CVE-2026-118938",
  "display_id": "CVE-2026-118938",
  "ghsa_id": "GHSA-6jfm-qx2v-27jg",
  "euvd_id": "EUVD-2026-114515",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Dotted attribute-path safety-check bypass in fickling",
  "summary": "fickling through version 0.1.12 can incorrectly approve pickles containing dotted attribute references during safety analysis. An attacker who can supply a pickle that is subsequently loaded through the affected loading path can cause arbitrary code execution despite the safety check.",
  "mitigation": "Do not load untrusted pickles with fickling, including when its safety check reports that they are safe; reject them or process them in an isolated environment. No fixed version is identified in the evidence, so track for a release that explicitly corrects dotted attribute-path analysis before relying on this check.",
  "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": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 12.845077283333334,
  "t0_at": "2026-10-30T21:19:13.015000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-31T01:31:51.122882+00:00",
      "days": 0.17544106344907406,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T21:19:13.015000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-30T21:19:13.015000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-30T21:19:13.015000+00:00",
      "url": "https://github.com/advisories/GHSA-6jfm-qx2v-27jg"
    }
  }
}

published 2026-10-31 01:18Z
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.