Cyber & AI intelligence
Wasteland.
Briefs indexed2597
Issues28
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-81204 2026-09-10

CVE-2026-81204: Critical Code Injection in IBM Langflow OSS

"IBM disclosed a critical (CVSS 9.8) code injection flaw in Langflow OSS that, per the vendor advisory, could allow a remote attacker to execute arbitrary code during graph construction."

IBM disclosed a critical (CVSS 9.8) code injection flaw in Langflow OSS that, per the vendor advisory, could allow a remote attacker to execute arbitrary code during graph construction.

What Is It

CVE-2026-81204 is a code injection vulnerability (CWE-94) in IBM Langflow OSS. According to IBM's advisory, the flaw "could allow a remote attacker to execute arbitrary code due to code injection during graph construction." The CVE is recorded as published on 2026-09-10 by IBM PSIRT ([email protected]) and carries NVD status "Received," meaning NVD analysis is not yet complete.

One caveat on the identifier itself: CVE-2026-81204 sits well outside the block of CVE IDs actually issued so far in 2026; September 2026 assignments are several orders of magnitude lower. Readers should confirm the identifier against NVD and the IBM advisory directly before using it to drive ticketing, scanning signatures, or inventory queries; the technical details below reflect the record as supplied and have not been independently corroborated against a live NVD entry.

Why It Matters

The record scores the issue CVSS 3.1 base 9.8 (CRITICAL) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Every factor in that vector favors the attacker: network attack vector, low attack complexity, no privileges required, and no user interaction. The scored impact is full compromise of confidentiality, integrity, and availability; exploitability subscore 3.9, impact subscore 5.9.

In practical terms, if the scored vector holds, anything that can reach the Langflow graph-construction path over the network could potentially run code on the host. Note that IBM's own advisory text does not state that the attacker is unauthenticated; that reading comes from the PR:N component of the CVSS vector, not from the vendor's description. The precise preconditions for exploitation should be confirmed against the advisory.

This CVE does not appear in the supplied CISA KEV data, so there is no confirmed evidence of active exploitation in the material reviewed here. Readers can check the live catalog themselves at the link in Sources below.

What's Vulnerable

Those CPE strings are worth treating with caution rather than as authoritative applicability data. NVD does not generate CPE applicability configurations for records still in "Received" status; that work happens during analysis, which the record itself says has not occurred. A record cannot simultaneously be un-analyzed and carry NVD-assigned CPE matches, so the two fields contradict each other. The strings are reproduced here as supplied; they should not be loaded into a scanner or asset-matching query until they can be confirmed against a live NVD entry.

The affected range covers the entire 1.x line up to and including 1.11.5.

Patch Status

The supplied NVD record contains no fixed-version string and no CISA-mandated due date. The single reference is IBM's support advisory (node 7286666), which is the authoritative source for remediation guidance, for any fixed build number, and for confirming the correct CVE identifier. Operators running Langflow OSS 1.0.0–1.11.5 should consult that advisory directly for the patched release and any interim mitigations.

Given the severity of the scored profile, restricting network exposure of Langflow instances to trusted networks is a reasonable interim posture while the advisory is reviewed.

Sources