PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-104335 IBM CVE debrief

IBM Langflow OSS versions 1.0.0 through 1.12.2 are vulnerable to improper access control, allowing remote authenticated attackers to execute arbitrary code. This high-severity vulnerability requires defenders to assess exposure and prioritize verifying proper access controls to prevent potential arbitrary code execution. The CVE record and source item provide details on the vulnerability, including its CVSS score of 8.8. Defenders should review Langflow OSS deployments and ensure proper access controls are in place.

Vendor
IBM
Product
Langflow OSS
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-06
Original CVE updated
2026-10-08
Advisory published
2026-10-06
Advisory updated
2026-10-08

Who should care

Defenders responsible for Langflow OSS deployments should assess exposure and prioritize verifying proper access controls to prevent potential arbitrary code execution.

Why it matters

CVE-2026-104335 is a high-severity vulnerability in Langflow OSS that allows remote authenticated attackers to execute arbitrary code. Defenders should prioritize verifying exposure and assessing potential impact, focusing on Langflow OSS deployments and ensuring proper access controls are in place.

  • Potential arbitrary code execution on vulnerable Langflow OSS systems
  • Need to verify proper access controls are in place to prevent exploitation
  • Possible impact on system integrity and confidentiality if exploited

Technical summary

The CVE record describes a vulnerability in Langflow OSS, allowing remote authenticated attackers to execute arbitrary code due to improper access control. The affected versions are 1.0.0 through 1.12.2. This high-severity vulnerability has a CVSS score of 8.8, indicating a significant risk to Langflow OSS deployments. Defenders should prioritize verifying exposure and assessing potential impact, focusing on Langflow OSS deployments and ensuring proper access controls are in place.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, focusing on Langflow OSS deployments and ensuring proper access controls are in place.

Recommended defensive actions

  • Verify Langflow OSS deployments to ensure proper access controls are in place
  • Assess potential impact of arbitrary code execution on Langflow OSS systems
  • Review and update Langflow OSS versions to ensure they are not vulnerable

Evidence notes

The CVE record and source item provide details on the vulnerability, including its CVSS score of 8.8 and affected versions of Langflow OSS. The vulnerability allows remote authenticated attackers to execute arbitrary code due to improper access control. Defenders should verify exposure and assess potential impact, focusing on Langflow OSS deployments and ensuring proper access controls are in place. The source item and CVE record are the primary sources of information for this debrief.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-104335 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-104335

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-104335 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-104335

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Langflow OSS is affected by multiple vulnerabilities

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/104xxx/CVE-2026-104335.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://www.ibm.com/support/pages/node/7290694

    Supplemental source - vendor-advisory, patch

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.