PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-97680 IBM CVE debrief

IBM Langflow OSS 1.0.0 through 1.12.2 could allow a remote authenticated attacker to obtain sensitive information or inject malicious data due to improper access control in the vertex result caching subsystem. This high-severity vulnerability affects defenders and security teams responsible for IBM Langflow OSS deployments, particularly in environments with authenticated remote access. They should assess potential exposure and prioritize verification and remediation efforts to prevent data leakage or injection attempts.

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

Who should care

Defenders and security teams responsible for IBM Langflow OSS deployments, particularly in environments with authenticated remote access, should assess potential exposure and prioritize verification and remediation efforts.

Why it matters

CVE-2026-97680 is a high-severity vulnerability in IBM Langflow OSS that could allow remote authenticated attackers to obtain sensitive information or inject malicious data. Defenders should prioritize verifying exposure, assessing potential impacts, and updating access controls to prevent data leakage or injection attempts.

  • Potential data leakage or exposure of sensitive information
  • Possible injection of malicious data through the vertex result caching subsystem
  • Need for verification of Langflow OSS version and deployment context
  • Priority for updating access controls and monitoring for potential attacks

Technical summary

IBM Langflow OSS 1.0.0 through 1.12.2 is vulnerable to improper access control in the vertex result caching subsystem, allowing a remote authenticated attacker to obtain sensitive information or inject malicious data. The vulnerability has a high CVSS score of 8.3 and is considered a high-severity issue. Defenders should prioritize verifying exposure, assessing potential impacts, and updating access controls to prevent data leakage or injection attempts.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential data leakage or injection in Langflow OSS deployments, particularly in environments with authenticated remote access.

Recommended defensive actions

  • Verify Langflow OSS version and check if it falls within the affected range (1.0.0 to 1.12.2)
  • Assess the deployment context for potential exposure, particularly in environments with authenticated remote access
  • Review and update access controls for the vertex result caching subsystem
  • Monitor for potential data leakage or injection attempts

Evidence notes

The CVE record and source item provide details on the vulnerability in IBM Langflow OSS, including affected versions and a brief description of the issue.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-97680 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-97680 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/97xxx/CVE-2026-97680.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.