{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41947 exists.","fix":"No fix has been published for CVE-2026-41947 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-41947 is a critical missing authorization vulnerability in langgenius dify, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-41947 and fix it if it is affected.\n\nWhat it is: CVE-2026-41947 is a critical missing authorization vulnerability in langgenius dify, published on 18 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41947 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-41947/ (Markdown: https://insights.sbomify.com/CVE-2026-41947/index.md)","id":"CVE-2026-41947","markdown":"https://insights.sbomify.com/CVE-2026-41947/index.md","name":"CVE-2026-41947","record":{"aliases":["GHSA-48v9-p8g8-55vg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Dify AI platform","requires_auth":"none","summary":"Authenticated editors can bypass tenant ownership checks to redirect application traffic to attacker-controlled trace providers, exposing sensitive data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"dify","vendor":"dify"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Dify before version 1.14.2 contains an authorization bypass vulnerability that allows authenticated editor users to set and enable trace configurations for any application regardless of tenant ownership. Attackers can exploit missing tenant ownership checks in the trace configuration endpoints to redirect all messages and responses from victim applications to attacker-controlled LLM trace providers. NOTE: Dify Cloud allows unauthenticated free self-registration, making account creation trivially accessible to any attacker.","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 \u003c 1.14.2 Authorization Bypass via Trace Configuration Endpoints","id":"CVE-2026-41947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access","id":"CVE-2026-41948"},"packages":[],"prev":{"headline":"WebPros cPanel \u0026 WHM and WP2 (WordPress Squared) Missing Authentication for Critical Function","id":"CVE-2026-41940"},"products":["dify"],"published":"2026-05-18","related":[{"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["langgenius"]},"summary":"Authenticated editors can bypass tenant ownership checks to redirect application traffic to attacker-controlled trace providers, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-41947/"}