CVE-2026-86535

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

GHSA-77gh-6cq5-g8qw ↗EUVD-2026-91452 ↗

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.
apache software foundation Apache Thrift < 0.25.0
fixed in 0.25.0
ETK-2026-345, permanent identifier
pkg:npm/thrift
19d 04h 52msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h28m
0
+2h
+6h
+8h
+10h
+12h

description

Apache Thrift Node.js bindings using TJSONProtocol are affected in releases before 0.25.0. The flaws may allow modification of object prototype attributes or processing that does not terminate; use of TJSONProtocol is the stated affected condition.

mitigation

Upgrade Apache Thrift to version 0.25.0 or later. Prioritize systems that use the Node.js bindings with TJSONProtocol.

fixed in 0.25.0

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.
0.34%25th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 11:38Z
Δ 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: an exploit technique exists, 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-02 11:38Z
    ghsa: trigger signal, started the run
  2. 2026-10-02 11:38Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-345",
  "cve_id": "CVE-2026-86535",
  "display_id": "CVE-2026-86535",
  "ghsa_id": "GHSA-77gh-6cq5-g8qw",
  "euvd_id": "EUVD-2026-91452",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Prototype pollution and infinite loop in Apache Thrift Node.js bindings",
  "summary": "Apache Thrift Node.js bindings using TJSONProtocol are affected in releases before 0.25.0. The flaws may allow modification of object prototype attributes or processing that does not terminate; use of TJSONProtocol is the stated affected condition.",
  "mitigation": "Upgrade Apache Thrift to version 0.25.0 or later. Prioritize systems that use the Node.js bindings with TJSONProtocol.",
  "vendor": "apache software foundation",
  "product": "Apache Thrift",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.25.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "0.25.0"
      ],
      "package_name": "thrift",
      "purl": "pkg:npm/thrift"
    }
  ],
  "cwes": null,
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
  "epss_score": 0.0034,
  "epss_percentile": 0.2599,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.398498866666667,
  "t0_at": "2026-10-02T11:38:16.628000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T11:38:16.628000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T11:38:16.628000+00:00",
      "url": "https://github.com/advisories/GHSA-77gh-6cq5-g8qw"
    }
  }
}

published 2026-10-02 14:53Z
last change 2026-10-21 19:22Z

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.