{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-57575 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-57575 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-57575 is a medium-severity server-side request forgery vulnerability in misskey-dev misskey, published on 10 Jul 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-57575 and fix it if it is affected.\n\nWhat it is: CVE-2026-57575 is a medium-severity server-side request forgery vulnerability in misskey-dev misskey, published on 10 Jul 2026. 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-2026-57575 in the wild and no public exploit code.\n\nAffected product: misskey-dev misskey. 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-57575/ (Markdown: https://insights.sbomify.com/CVE-2026-57575/index.md)","id":"CVE-2026-57575","markdown":"https://insights.sbomify.com/CVE-2026-57575/index.md","name":"CVE-2026-57575","record":{"aliases":["GHSA-jvcx-f39m-5xrj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Misskey social platform","requires_auth":"none","summary":"Remote attackers can bypass SSRF protections in Misskey's URL preview to trigger internal network requests, though data exfiltration is limited.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Misskey is an open source, federated social media platform. Prior to 2026.6.0, Misskey contains a Server-Side Request Forgery (SSRF) vulnerability in URL preview functionality in UrlPreviewService. Due to missing network restrictions before establishing outbound connections, a remote attacker can cause the Misskey server to initiate HTTP requests to loopback, private, or link-local services. Because IP address validation takes place after the request has been sent and the process is subsequently rejected, no sensitive internal data is believed to be transmitted back or exposed to the attacker. This issue is fixed in version 2026.6.0.","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":"Misskey: SSRF bypass in URL Preview","id":"CVE-2026-57575","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"plone.app.dexterity and plone.app.contenttypes have a Denial of Service due to excessive title or description length","id":"CVE-2026-57576"},"packages":[],"prev":{"headline":"Misskey: TOTP tokens can be reused","id":"CVE-2026-57574"},"products":["misskey"],"published":"2026-07-10","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":"2026-07-14","vendors":["misskey-dev"]},"summary":"Remote attackers can bypass SSRF protections in Misskey's URL preview to trigger internal network requests, though data exfiltration is limited.","url":"https://insights.sbomify.com/CVE-2026-57575/"}