CVE-2026-7871: Insecure Deserialization in Redis Cache Backend
IBM Langflow OSS 1.0.0 through 1.10.0 allows users with Redis access to execute arbitrary code with full application privileges, compromising all secrets, data, and system integrity.
Metrics
- CVSS v3.1
- 9.8
- Severity
- CRITICAL
- Fixed in
- —
- Affected Products
- 1
HarborGuard Analysis
Synopsis
This is an insecure deserialization vulnerability in IBM Langflow OSS versions 1.0.0 through 1.10.0, affecting the Redis cache backend. The vulnerability is reachable over the network, requires no authentication, and has no conditions the attacker must meet before triggering it. Successful exploitation gives an attacker arbitrary code execution with full application privileges, exposing all secrets, data, and system integrity. No upstream fix has been published yet; HarborGuard is tracking the advisory and will surface a patched rebuild the moment one becomes available.
HarborGuard Coverage
Detection is available across every HarborGuard environment: the CVE is ingested from upstream advisory feeds within minutes of publication and matched against customer images in connected registries and CI/CD pipelines, including custom-built images that bundle IBM Langflow OSS. Any image carrying an affected version (1.0.0 through 1.10.0) is flagged automatically.
AvailableHarborGuard is capable of scoring this finding at CVSS 9.8 Critical and weighting it against each environment's compliance policy to determine urgency and routing. Findings are dispatched to the appropriate team inbox within each customer organization based on configured policy rules, without requiring manual triage.
AvailableBecause no upstream fix version has been published, HarborGuard re-evaluates the advisory on every ingest cycle and will make a patched-image rebuild available the moment IBM publishes a remediated release. In the meantime, customers can apply compensating controls through HarborGuard's policy engine, such as network-isolation rules that restrict Redis-endpoint exposure.
Pending upstreamExploit Conditions
- Network reachabilityRequired
The vulnerable component is exposed over the network; an attacker must be able to reach the service's Redis endpoint remotely to deliver a malicious serialized payload.
- AuthenticationNot required
No credentials or account of any privilege level are required to reach the vulnerable code path.
- Victim interactionNot required
Exploitation is entirely attacker-driven and does not require any action from a user or administrator of the affected system.
- Attack complexityDetail
Exploit conditions are reliable and free of race conditions or environmental dependencies, meaning a prepared payload succeeds consistently against any unpatched instance.
Blast Radius
- Executes arbitrary code with full application privileges, giving the attacker complete control of the Langflow OSS process.
- Reads all application secrets, including API keys, credentials, and session tokens stored or accessible by the application.
- Modifies or destroys any data the application can access, including persisted workflow definitions and user records.
- Crashes or degrades the application and its dependent services at will, causing sustained service disruption.
How HarborGuard Handles This
Available on HarborGuard: any image containing IBM Langflow OSS 1.0.0 through 1.10.0 is matched against this CVE within minutes of the advisory entering upstream feeds, and a Critical-severity finding is raised in the affected customer environment's queue according to its compliance policy. Because IBM has not yet published a fix version, no patched-image rebuild is available at this time. HarborGuard re-checks the advisory on every ingest cycle and will automatically initiate a rebuild and, for customers with auto-remediation enabled, open a patch PR against affected workloads as soon as an upstream fix is released. While waiting for an upstream patch, customers can use HarborGuard's network-policy controls to restrict which workloads are permitted to connect to Redis endpoints, reducing the attack surface without requiring application changes. Egress filtering and feature-flag gating on the Redis cache backend are additional compensating controls worth evaluating in the interim.
- IBM / Langflow OSS≤ 1.10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H