CVE-2026-3357
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Langflow Desktop 1.6.0 through 1.8.2 Langflow could allow an authenticated user to execute arbitrary code on the system, caused by an insecure default setting which permits the deserialization of untrusted data in the FAISS component.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM Langflow Desktop versions 1.6.0 through 1.8.2 contains an insecure default configuration that allows deserialization of untrusted data in the FAISS (Facebook AI Similarity Search) component, enabling authenticated users to achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.6.0, < 1.8.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Langflow versionRun 'pip show langflow' or check your package manager to find the installed version of LangflowAffected if The installed version is >= 1.6.0 and < 1.8.3
-
Verify FAISS is installedRun 'pip show faiss-cpu' or 'pip show faiss-gpu' to confirm the FAISS library is present in your environmentAffected if FAISS is installed and available to Langflow
-
Check for active flows using FAISSInspect your Langflow flows or configurations for any vector store components that utilize FAISS for similarity searchAffected if Any flow is configured to use FAISS as a vector store backend
-
Inspect FAISS deserialization settingsReview Langflow configuration files or environment variables for settings related to FAISS data loading, particularly any that control deserialization of stored vectorsAffected if FAISS is configured to allow loading/deserialization of data without validation
You are affected if your Langflow version is 1.6.0 through 1.8.2 and FAISS is installed and being used to deserialize untrusted vector data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.8.3
Upgrade to a patched version of IBM Langflow Desktop. If immediate patching is not feasible, review and restrict FAISS deserialization settings to reject untrusted data sources.
Langflow 1.8.3 or later
- Back up your Langflow data and configuration before upgrading
- Upgrade Langflow to version 1.8.3 or later using your package manager (e.g., pip install langflow>=1.8.3)
- Verify the upgrade completed successfully by checking the installed version
- Restart the Langflow service to ensure the new version is running
- Confirm that FAISS component functionality is working correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data