PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-101329 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 obtain sensitive information. This medium-severity vulnerability, with a CVSS score of 6.5, was published on October 6, 2026, and has not been modified since then. Defenders responsible for Langflow OSS deployments, especially those with remote authenticated access, should assess exposure and prioritize access control adjustments to prevent unauthorized access and information disclosure.

Vendor
IBM
Product
Langflow OSS
CVSS
MEDIUM 6.5
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, especially those with remote authenticated access, should assess exposure and prioritize access control adjustments.

Why it matters

CVE-2026-101329 is a medium-severity vulnerability in IBM Langflow OSS that allows remote authenticated attackers to obtain sensitive information due to improper access control. Defenders should prioritize verifying exposure, assessing access control needs, and updating configurations to prevent unauthorized access and information disclosure.

  • Verify exposure of Langflow OSS deployments to unauthorized access
  • Assess and adjust access control configurations to prevent information disclosure
  • Review and update access control policies and procedures

Technical summary

IBM Langflow OSS versions 1.0.0 through 1.12.2 are vulnerable to improper access control, allowing remote authenticated attackers to obtain sensitive information. The vulnerability has a CVSS score of 6.5 and a MEDIUM severity rating. Defenders should prioritize verifying exposure of Langflow OSS deployments, especially those with remote authenticated access, and assess the need for access control adjustments.

Defensive priority

Defenders should prioritize verifying exposure of Langflow OSS deployments, especially those with remote authenticated access, and assess the need for access control adjustments.

Recommended defensive actions

  • Verify Langflow OSS deployments for exposure, especially those with remote authenticated access
  • Assess the need for access control adjustments
  • Review and update access control configurations

Evidence notes

The CVE Program record and NVD vulnerability detail provide official information on the vulnerability. IBM's vendor advisory is also available. The vulnerability affects Langflow OSS versions 1.0.0 through 1.12.2, and defenders should verify exposure and assess access control needs. The CVE record was published on October 6, 2026, and has not been modified since then. The NVD entry is currently MEDIUM with a CVSS score of 6.5. The source item providing details on the vulnerability is c

Sources and references

Verified primary and authoritative sources

  • CVE-2026-101329 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-101329 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/101xxx/CVE-2026-101329.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.