CVE-2026-88962

validatedZero produced an exploit or a check.

GHSA-g2pv-fx5p-45j2 ↗EUVD-2026-94110 ↗

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
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-830, permanent identifier
+1h55mTTV
51mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+1h55magent stopped
0
+1h

description

Langflow OSS versions 1.0.0 through 1.12.2 are affected by improper control of code generation. A remote attacker with valid authentication may be able to execute arbitrary code.

mitigation

Restrict access to Langflow OSS to trusted, least-privileged authenticated users and limit its network exposure. Monitor vendor updates and upgrade promptly when a fixed release is published.

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.81%56th percentile
agent run time
51m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 00:02Z
Δ 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-07 00:02Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-830",
  "cve_id": "CVE-2026-88962",
  "display_id": "CVE-2026-88962",
  "ghsa_id": "GHSA-g2pv-fx5p-45j2",
  "euvd_id": "EUVD-2026-94110",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper code generation control in Langflow OSS",
  "summary": "Langflow OSS versions 1.0.0 through 1.12.2 are affected by improper control of code generation. A remote attacker with valid authentication may be able to execute arbitrary code.",
  "mitigation": "Restrict access to Langflow OSS to trusted, least-privileged authenticated users and limit its network exposure. Monitor vendor updates and upgrade promptly when a fixed release is published.",
  "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": [
    94
  ],
  "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.0081,
  "epss_percentile": 0.5613,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 51.15889248333333,
  "t0_at": "2026-10-07T00:02:53.758000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-07T01:57:36.861233+00:00",
      "days": 0.07966554667824075,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T00:02:53.758000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-07T00:02:53.758000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T00:02:53.758000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-88962"
    }
  }
}

published 2026-10-07 01:06Z
last change 2026-10-21 05:31Z

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.