Protected-data compromise via weak Fernet key derivation
Published Aug 5, 2026 · Updated Aug 5, 2026
Weak key derivation in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote attackers to read or alter Fernet-protected data. IBM identifies ensure_fernet_key() as the affected locus but has not disclosed how the function derives a weak key from untrusted input. Exploitation requires no account or user interaction, but IBM rates the attack as high complexity; successful use compromises protected data without interrupting service.
Summary
What happened
Weak key derivation in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote attackers to read or alter Fernet-protected data. IBM identifies ensure_fernet_key() as the affected locus but has not disclosed how the function derives a weak key from untrusted input. Exploitation requires no account or user interaction, but IBM rates the attack as high complexity; successful use compromises protected data without interrupting service.
The record
- CVE
- CVE-2026-9205
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-338, T1555
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.3
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
No public exploit references are available in this record.
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