{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-46385 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46385 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46385 is a high-severity server-side request forgery vulnerability in Emby Windows, published on 20 Jul 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-46385 and fix it if it is affected.\n\nWhat it is: CVE-2025-46385 is a high-severity server-side request forgery vulnerability in Emby Windows, published on 20 Jul 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-46385 in the wild and no public exploit code.\n\nAffected product: Emby Windows. 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-46385/ (Markdown: https://insights.sbomify.com/CVE-2025-46385/index.md)","id":"CVE-2025-46385","markdown":"https://insights.sbomify.com/CVE-2025-46385/index.md","name":"CVE-2025-46385","record":{"aliases":["GHSA-89p2-5qg7-rj57"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Emby Media Server","requires_auth":"none","summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in Emby Media Server to access internal resources or bypass security controls.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCD","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"CWE-918 Server-Side Request Forgery (SSRF)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-side request forgery in Windows","id":"CVE-2025-46385","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in MediaBrowser","id":"CVE-2025-46386"},"packages":[],"prev":{"headline":"File upload in Windows","id":"CVE-2025-46384"},"products":["Windows"],"published":"2025-07-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-07-21","vendors":["Emby"]},"summary":"An attacker can exploit a Server-Side Request Forgery vulnerability in Emby Media Server to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2025-46385/"}