Skip to main content
VulnerabilityPublished

CVE-2026-5026: langflow · Cross-site Scripting

Affects langflowSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.0 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
langflow-ailangflowAffected
  • =0
Fixed in–
PyPIlangflowpkg:pypi/langflowOther threatsAffected
  • =0
Fixed in–
GitHublangflowpkg:github/langflowOther threatsAffected
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-5026, organizations should implement strict input validation and sanitization on all SVG uploads, ensuring that any embedded scripts or potentially malicious content are removed or neutralized before serving the files. Employing a whitelist approach to allowed SVG elements and attributes can reduce risk. If possible, restrict or disable SVG uploads entirely unless absolutely necessary. Use Content Security Policy (CSP) headers to limit the execution of inline scripts and restrict sources of executable code in browsers. Monitor and audit file upload endpoints for unusual activity and implement rate limiting to reduce abuse. Ensure that authentication tokens are stored securely using HttpOnly and Secure cookie flags to prevent theft via JavaScript. Regularly update langflow to the latest versions once patches become available. Additionally, educate users about the risks of interacting with untrusted SVG content and encourage reporting of suspicious files. Consider isolating SVG rendering in sandboxed environments or using server-side rendering techniques to avoid direct client execution of SVG scripts.

Description

The '/api/v1/files/images/{flow_id}/{file_name}' endpoint serves SVG files with the 'image/svg+xml' content type without sanitizing their content. Since SVG files can contain embedded JavaScript, an attacker can upload a malicious SVG that executes arbitrary JavaScript when viewed by other users, leading to stored cross-site scripting (XSS). This allows stealing authentication tokens stored in cookies, including JWT access and refresh tokens.

References

Community reviews

Loading reviews…