CVE-2026-110186

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

EUVD-2026-113134 ↗

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.
IBM Langflow OSS >= 1.0.0, <= 1.12.8
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-2981Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 23msince last run
45mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h53m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Langflow OSS 1.0.0 through 1.12.8 can permit remote code execution through inadequate controls on generated code. Exposure is most relevant where authentication is disabled and affected flows or agent-communication endpoints are publicly reachable.

mitigation

Enable authentication and remove public access to flows and agent-communication endpoints. Restrict these services to trusted networks until IBM provides an updated release.

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.
–
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
45m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 15:15Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-29 15:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2981",
  "cve_id": "CVE-2026-110186",
  "display_id": "CVE-2026-110186",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-113134",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper code generation in Langflow OSS",
  "summary": "Langflow OSS 1.0.0 through 1.12.8 can permit remote code execution through inadequate controls on generated code. Exposure is most relevant where authentication is disabled and affected flows or agent-communication endpoints are publicly reachable.",
  "mitigation": "Enable authentication and remove public access to flows and agent-communication endpoints. Restrict these services to trusted networks until IBM provides an updated release.",
  "vendor": "IBM",
  "product": "Langflow OSS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.0.0, <= 1.12.8"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Langflow OSS",
      "purl": null
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.97664793333333,
  "t0_at": "2026-10-29T15:15:59.506000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T15:15:59.506000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T15:15:59.506000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110186"
    }
  }
}

published 2026-10-29 15:24Z
last change 2026-10-29 16:58Z

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.