Code execution via unsigned Redis cache deserialization
Published Jun 30, 2026 · Updated Jun 30, 2026
Insecure deserialization in IBM Langflow OSS 1.0.0 through 1.10.0 allows remote attackers with Redis access to execute arbitrary code. The Redis cache service passes unsigned cache values to dill.loads(), so a crafted serialized object executes when any worker reads it. Reachability requires network access to the configured Redis instance; execution inherits the Langflow application's privileges and access to its secrets and data.
Summary
What happened
Insecure deserialization in IBM Langflow OSS 1.0.0 through 1.10.0 allows remote attackers with Redis access to execute arbitrary code. The Redis cache service passes unsigned cache values to dill.loads(), so a crafted serialized object executes when any worker reads it. Reachability requires network access to the configured Redis instance; execution inherits the Langflow application's privileges and access to its secrets and data.
The record
- CVE
- CVE-2026-7871
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-502, T1210
- 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
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