{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-63386 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-63386 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63386 is a critical vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-63386 and fix it if it is affected.\n\nWhat it is: CVE-2025-63386 is a critical vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-63386 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2025-63386/ (Markdown: https://insights.sbomify.com/CVE-2025-63386/index.md)","id":"CVE-2025-63386","markdown":"https://insights.sbomify.com/CVE-2025-63386/index.md","name":"CVE-2025-63386","record":{"aliases":["GHSA-vjm9-gq46-wc5j"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Dify AI platform","requires_auth":"none","summary":"Insecure CORS policy in Dify allows arbitrary domains to make authenticated requests, potentially leading to account takeover or data exposure.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dify","vendor":"langgenius"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"A Cross-Origin Resource Sharing (CORS) misconfiguration vulnerability exists in Dify v1.9.1 in the /console/api/setup endpoint. The endpoint implements an insecure CORS policy that reflects any Origin header and enables Access-Control-Allow-Credentials: true, permitting arbitrary external domains to make authenticated requests. NOTE: the Supplier disputes this because the endpoint configuration is intentional to support bootstrap.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Misconfiguration in n/a","id":"CVE-2025-63386","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-63387"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-63384"},"products":["n/a"],"published":"2025-12-18","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-56157","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":9.8,"headline":"Unsanitized Input in langgenius/dify","id":"CVE-2025-3466","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":9.1,"headline":"Misconfiguration in n/a","id":"CVE-2025-63388","kev_date_added":null,"published":"2025-12-18"},{"cvss_score":8.8,"headline":"Code Injection in langgenius/dify","id":"CVE-2024-10252","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8.1,"headline":"Authentication Bypass in langgenius/dify","id":"CVE-2024-12776","kev_date_added":null,"published":"2025-03-20"},{"cvss_score":8,"headline":"XSS Vulnerability in langgenius/dify","id":"CVE-2025-3467","kev_date_added":null,"published":"2025-07-07"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-11","vendors":["n/a"]},"summary":"Insecure CORS policy in Dify allows arbitrary domains to make authenticated requests, potentially leading to account takeover or data exposure.","url":"https://insights.sbomify.com/CVE-2025-63386/"}