CVE-2026-81268

Received Received - Intake

IBM Langflow OSS Session Key Exposure After User Deactivation

Publication date: 2026-09-10

Last updated on: 2026-09-10

Assigner: IBM Corporation

Description

IBM Langflow OSS 1.0.0 through 1.11.5 could allow a remote authenticated attacker to execute flows and obtain sensitive information due to insufficient session expiration of API keys after user deactivation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-10

Last Modified

2026-09-10

Generated

2026-09-11

AI Q&A

2026-09-11

EPSS Evaluated

N/A

NVD

CVE-2026-81268

Affected Vendors & Products

Vendor	Product	Version / Range
ibm	langflow_oss	From 1.0.0 (inc) to 1.11.5 (inc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-613	According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

Attack-Flow Graph

Executive Summary

IBM Langflow OSS versions 1.0.0 through 1.11.5 have a vulnerability where API keys remain valid even after a user is deactivated. This allows remote authenticated attackers to execute flows and access sensitive information due to insufficient session expiration.

Impact Analysis

If you use IBM Langflow OSS in versions 1.0.0 to 1.11.5, an attacker with valid credentials could exploit this to run unauthorized flows and steal sensitive data. This could lead to data breaches, unauthorized access, or other security incidents.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR and HIPAA requirements for data protection and access controls. Organizations may face compliance violations, legal penalties, and reputational damage.

Mitigation Strategies

Rotate all API keys immediately after deactivating any user accounts. Ensure session expiration policies are enforced for API keys. Monitor for unauthorized flow executions or sensitive data access.

Hi! I’m here to help you understand CVE-2026-81268. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70