CVE-2026-97676

validatedZero produced an exploit or a check.

GHSA-jm65-m624-cgvm ↗EUVD-2026-94127 ↗

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.
IBM Langflow OSS >= 1.0.0, <= 1.12.2
ETK-2026-848, permanent identifier
+5h58mTTV
30mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+5h58magent stopped
0
+2h
+4h

description

IBM Langflow OSS versions 1.0.0 through 1.12.2 are affected by a sandbox-escape flaw in code handling. An attacker with valid authentication may execute code on the affected system.

mitigation

Restrict access to trusted, necessary users and isolate Langflow deployments from sensitive systems and credentials. Apply a vendor-provided update when a fixed release is identified.

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.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.55%44th percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 23:58Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-10-06 23:58Z
    ghsa: trigger signal, started the run
  2. 2026-10-06 23:58Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-848",
  "cve_id": "CVE-2026-97676",
  "display_id": "CVE-2026-97676",
  "ghsa_id": "GHSA-jm65-m624-cgvm",
  "euvd_id": "EUVD-2026-94127",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated sandbox escape in IBM Langflow OSS",
  "summary": "IBM Langflow OSS versions 1.0.0 through 1.12.2 are affected by a sandbox-escape flaw in code handling. An attacker with valid authentication may execute code on the affected system.",
  "mitigation": "Restrict access to trusted, necessary users and isolate Langflow deployments from sensitive systems and credentials. Apply a vendor-provided update when a fixed release is identified.",
  "vendor": "IBM",
  "product": "Langflow OSS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.0, <= 1.12.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Langflow OSS",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0055,
  "epss_percentile": 0.448,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 29.5830813,
  "t0_at": "2026-10-06T23:58:57.606000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-07T05:57:15.603518+00:00",
      "days": 0.24881941571759258,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T23:58:57.606000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-06T23:58:57.606000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T23:58:57.606000+00:00",
      "url": "https://github.com/advisories/GHSA-jm65-m624-cgvm"
    }
  }
}

published 2026-10-07 05:27Z
last change 2026-10-21 16:15Z

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.