Credential disclosure via reversible encryption key derivation
Published Jun 30, 2026 · Updated Jun 30, 2026
Weak credential encryption in IBM Langflow OSS 1.0.0 through 1.10.0 allows remote attackers to decrypt all stored credentials. The credential encryption code seeds Python's Mersenne Twister with SECRET_KEY to derive a deterministic Fernet key, or uses a long SECRET_KEY directly. Exploitation requires obtaining that deployment secret, after which API keys, database passwords, and OAuth tokens can be decrypted offline.
Summary
What happened
Weak credential encryption in IBM Langflow OSS 1.0.0 through 1.10.0 allows remote attackers to decrypt all stored credentials. The credential encryption code seeds Python's Mersenne Twister with SECRET_KEY to derive a deterministic Fernet key, or uses a long SECRET_KEY directly. Exploitation requires obtaining that deployment secret, after which API keys, database passwords, and OAuth tokens can be decrypted offline.
The record
- CVE
- CVE-2026-7874
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-338, T1555
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <=1.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Weak Fernet Key via random.seed() proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo