CVE-2026-3346
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.4 Lanflow is vulnerable to stored cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
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.4 are vulnerable to stored cross-site scripting (XSS). An authenticated user can inject arbitrary JavaScript code into the Web UI, which gets stored and executed when other users view the affected content. This can allow attackers to steal credentials or perform actions within a trusted user session.
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.4CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
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.
-
Identify if Langflow Desktop is installedCheck for Langflow Desktop installation by looking for the application in your system or by running 'langflow --version' or checking common installation directories.Affected if Langflow Desktop is not found on the system, the check is not applicable.
-
Determine the installed version of Langflow DesktopRun 'langflow --version' or check the application's about/properties section to retrieve the exact version number.Affected if The version cannot be determined, proceed with other checks.
-
Compare installed version against affected rangeCompare the retrieved version number to the affected range: 1.6.0 through 1.8.4. Versions 1.6.0, 1.6.1, 1.7.0, 1.7.1, 1.8.0, 1.8.1, 1.8.2, 1.8.3, and 1.8.4 are all affected.Affected if The installed version is 1.6.0, 1.6.1, 1.7.0, 1.7.1, 1.8.0, 1.8.1, 1.8.2, 1.8.3, or 1.8.4, indicating the environment is vulnerable.
-
Verify Web UI is accessibleConfirm that the Langflow Web UI is enabled and accessible by checking if the application serves HTTP/HTTPS on its configured port.Affected if The Web UI is accessible and the version is within the affected range, the stored XSS vulnerability can be triggered.
-
Confirm authentication is configuredCheck if user authentication is enabled in Langflow Desktop configuration, as this is an authenticated XSS requiring a user session.Affected if Authentication is enabled and the version falls within 1.6.0-1.8.4, an authenticated attacker could exploit the stored XSS.
If Langflow Desktop version 1.6.0 through 1.8.4 is installed with the Web UI accessible and authentication enabled, the environment is affected by this stored XSS vulnerability.
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.
From vendor dataUpgrade IBM Langflow Desktop to a version beyond 1.8.4 when available. As an interim measure, implement input validation and output encoding on all user-supplied content rendered in the Web UI, and configure Content Security Policy headers to mitigate XSS execution.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3346 — 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-3346 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