{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21866 exists.","fix":"No fix has been published for CVE-2026-21866 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21866 is a medium-severity cross-site scripting vulnerability in langgenius dify, published on 3 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-21866 and fix it if it is affected.\n\nWhat it is: CVE-2026-21866 is a medium-severity cross-site scripting vulnerability in langgenius dify, published on 3 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21866 exists.\n\nAffected product: langgenius dify. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-21866/ (Markdown: https://insights.sbomify.com/CVE-2026-21866/index.md)","id":"CVE-2026-21866","markdown":"https://insights.sbomify.com/CVE-2026-21866/index.md","name":"CVE-2026-21866","record":{"aliases":["GHSA-qpv6-75c2-75h4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"LLM app development platform","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts in user browsers via stored XSS in chat Mermaid diagrams, affecting Dify platform users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dify","vendor":"dify"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Dify is an open-source LLM app development platform. Prior to 1.11.2, Dify is vulnerable to a stored XSS issue when rendering Mermaid diagrams within chats. This occurs because Dify’s default Mermaid configuration uses securityLevel: loose, which allows potentially unsafe content to execute. This vulnerability is fixed in 1.11.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Dify - Stored XSS in chat","id":"CVE-2026-21866","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Reason: This candidate was issued in error.","id":"CVE-2026-21867"},"packages":[],"prev":{"headline":"Discourse topic conversion permission vulnerability for moderators","id":"CVE-2026-21865"},"products":["dify"],"published":"2026-03-03","related":[{"cvss_score":9.3,"headline":"Dify \u003c 1.14.2 Authorization Bypass via Trace Configuration Endpoints","id":"CVE-2026-41947","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":9.3,"headline":"Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access","id":"CVE-2026-41948","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":8.8,"headline":"Pandas Query Injection in langgenius/dify","id":"CVE-2025-0185","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.7,"headline":"Dify \u003c 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text","id":"CVE-2026-61461","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.4,"headline":"Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint","id":"CVE-2025-67732","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":8.2,"headline":"Dify \u003c 1.14.2 Authorization Bypass via File Preview Endpoint","id":"CVE-2026-41949","kev_date_added":null,"published":"2026-05-18"},{"cvss_score":6.5,"headline":"Server-Side Request Forgery (SSRF) in langgenius/dify","id":"CVE-2024-11822","kev_date_added":null,"published":"2025-03-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-04","vendors":["langgenius"]},"summary":"Attackers can execute arbitrary scripts in user browsers via stored XSS in chat Mermaid diagrams, affecting Dify platform users.","url":"https://insights.sbomify.com/CVE-2026-21866/"}