PatchSiren cyber security CVE debrief
CVE-2026-97676 IBM CVE debrief
IBM Langflow OSS versions 1.0.0 through 1.12.2 are vulnerable to a high-severity issue, CVE-2026-97676, allowing remote authenticated attackers to execute arbitrary code due to improper neutralization of special elements used in code. This results in a sandbox escape, posing significant risks to Langflow OSS deployments. Defenders responsible for these deployments should assess potential exposure, prioritize verification, and remediate affected versions to mitigate potential code execution risks.
- 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, particularly those using versions 1.0.0 through 1.12.2, should assess potential exposure and prioritize verification and remediation efforts.
Why it matters
CVE-2026-97676 is a high-severity vulnerability in Langflow OSS that allows remote authenticated attackers to execute arbitrary code, potentially leading to sandbox escapes and code execution risks. Defenders should prioritize verifying exposure, assessing potential risks, and remediating affected versions.
- Potential code execution risks in Langflow OSS deployments
- Sandbox escape vulnerability allowing arbitrary code execution
- Need for verification and remediation of affected versions
Technical summary
CVE-2026-97676 is a high-severity vulnerability in Langflow OSS, allowing remote authenticated attackers to execute arbitrary code due to improper neutralization of special elements used in code. This results in a sandbox escape. The vulnerability affects Langflow OSS versions 1.0.0 through 1.12.2, with a CVSS score of 8.8. Defenders should prioritize verifying exposure and assessing potential code execution risks in Langflow OSS deployments.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential code execution risks in Langflow OSS deployments, particularly for versions 1.0.0 through 1.12.2.
Recommended defensive actions
- Verify Langflow OSS version and assess exposure
- Review and update Langflow OSS to a version outside the affected range if possible
- Monitor for potential code execution attempts in Langflow OSS deployments
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 official CVE Program record (cve-org) and the NIST NVD detail page (nvd) offer source-provided CVE metadata and vulnerability assessments. However, the exact scope of affected deployments and specific code execution risks remain to be verified by defenders. Verification tasks should focus on confirming whether Langflow OSS versions 1.0.0 to 1.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-97676 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-97676
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-97676 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97676
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-97676.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.