Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guards (CVE-2026-76059) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-76059

Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guards

Answer in brief

CVE-2026-76059 records a Unknown severity vulnerability in Langflow is vulnerable to arbitrary code execution due to multiple incomplete code security controls and missing execution guards. The current sources do not mark it as known exploited. The current feed maps IBM/Langflow OSS (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 10, 2026Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps IBM/Langflow OSS (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
IBM/Langflow OSSgeneric	1.0.0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for IBM/Langflow OSS.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Source referenceibm.com

Upstream source description

IBM Langflow OSS 1.0.0 through 1.11.5 An attacker who could submit custom component source code could bypass the static security scanner by crafting an annotated class-body assignment that resolved to a dangerous callable through alias tracking; the resolved value was never checked against the dangerous callable blocklist due to the logic error. If the crafted component reached the runtime execution path, the attacker could cause arbitrary operating system commands to execute on the server in-process, with the privileges of the running service.

Quoted source text, attributed separately from HOL analysis.