CVE-2026-7874
Received Received - Intake

IBM Langflow Credential Disclosure via Weak Encryption

Vulnerability report for CVE-2026-7874, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-30

Last updated on: 2026-06-30

Assigner: IBM Corporation

Description

IBM Langflow OSS 1.0.0 through 1.10.0 Langflow could allow disclosure of all stored credentials due to the use of a weak and reversible key derivation mechanism for encryption at rest.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-30
Last Modified
2026-06-30
Generated
2026-07-01
AI Q&A
2026-06-30
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
ibm langflow_oss From 1.0.0 (inc) to 1.10.0 (inc)
ibm langflow From 1.0.0 (inc) to 1.10.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-338 The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-7874 is a critical vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0 that allows attackers to decrypt all stored credentials, such as API keys, database passwords, and OAuth tokens.

The root cause is the use of a weak and reversible key derivation mechanism for encryption at rest. Specifically, Python's non-cryptographic Mersenne Twister PRNG, seeded with the SECRET_KEY, is used to derive Fernet encryption keys.

If the SECRET_KEY is shorter than 32 characters, the derived encryption key becomes fully deterministic and reproducible by anyone with access to the SECRET_KEY. Even with longer keys, the raw SECRET_KEY is used directly as the Fernet key, making decryption trivial once the secret_key file is obtained.

Additionally, combined with a path traversal vulnerability, attackers could exfiltrate the secret_key file and decrypt all stored credentials offline without brute force.

Impact Analysis

This vulnerability can lead to the complete disclosure of all stored credentials within Langflow OSS, including sensitive information like API keys, database passwords, and OAuth tokens.

Attackers who gain access to the SECRET_KEY or exploit the related path traversal vulnerability can decrypt these credentials offline without needing to brute force, potentially leading to unauthorized access to connected systems and data.

The vulnerability has a high severity with a CVSS base score of 9.1, indicating a significant risk of confidentiality and integrity compromise.

Mitigation Strategies

IBM strongly recommends upgrading Langflow OSS to version 1.10.1 to address this vulnerability.

No workarounds or mitigations are provided for this issue.

Compliance Impact

This vulnerability allows attackers to decrypt all stored credentials, including sensitive information such as API keys, database passwords, and OAuth tokens. Such unauthorized disclosure of sensitive data can lead to violations of data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.

Because the encryption mechanism is weak and reversible, and attackers can exfiltrate the secret_key file to decrypt credentials offline, the risk of data breach is significantly increased. This undermines the confidentiality and integrity requirements of these standards.

Therefore, organizations using affected versions of Langflow OSS may face compliance issues if this vulnerability is exploited, potentially resulting in regulatory penalties and loss of trust.

Detection Guidance

This vulnerability involves the use of a weak and reversible key derivation mechanism in Langflow OSS versions 1.0.0 through 1.10.0, specifically related to the SECRET_KEY used for encrypting stored credentials.

Detection involves verifying the version of Langflow OSS running on your system and checking the length and usage of the SECRET_KEY file.

  • Check the installed Langflow OSS version to see if it falls within the vulnerable range (1.0.0 to 1.10.0). For example, use a command like: `langflow --version` or check the package version depending on your installation method.
  • Locate the SECRET_KEY file used by Langflow OSS. This file is critical because if it is shorter than 32 characters or accessible, the encryption key can be derived and credentials decrypted.
  • Use commands to inspect the SECRET_KEY file length and permissions, for example: `wc -c /path/to/secret_key` to check its length and `ls -l /path/to/secret_key` to check access permissions.
  • Monitor for any suspicious access or exfiltration attempts on the SECRET_KEY file, especially considering the related MCP path traversal vulnerability that could allow attackers to retrieve this file.

No specific detection commands or tools are provided by IBM, and no workarounds or mitigations exist other than upgrading to Langflow OSS version 1.10.1.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-7874. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart