{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-104817 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-104817 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-104817 is a high-severity server-side request forgery vulnerability in misskey-dev misskey, published on 13 Oct 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-104817 and fix it if it is affected.\n\nWhat it is: CVE-2026-104817 is a high-severity server-side request forgery vulnerability in misskey-dev misskey, published on 13 Oct 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-104817 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-104817/ (Markdown: https://insights.sbomify.com/CVE-2026-104817/index.md)","id":"CVE-2026-104817","markdown":"https://insights.sbomify.com/CVE-2026-104817/index.md","name":"CVE-2026-104817","record":{"aliases":["GHSA-4x7v-qx8f-g3p8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Misskey social platform","requires_auth":"none","summary":"Unauthenticated attackers can exhaust resources and probe internal networks via the RSS fetching API due to missing rate limits and size restrictions.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:L/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-405","name":"Asymmetric Resource Consumption (Amplification)"}],"description":"Misskey is an open source, federated social media platform. From 12.112.1 until 2026.7.0, the unauthenticated fetch-rss API lacks rate limiting and response-size restrictions and performs synchronous XML parsing. An attacker can trigger unbounded outbound HTTP requests and synchronous parsing, exhausting instance resources, amplifying requests toward third-party servers, or probing network-reachable services even when federation is disabled. This issue is fixed in version 2026.7.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: Lack of rate limiting and size restrictions in RSS fetching API","id":"CVE-2026-104817","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"react/http: Unbounded HTTP Client Response Header Buffering Leads to Memory Exhaustion DoS","id":"CVE-2026-104827"},"packages":[],"prev":{"headline":"Misskey: Cross-site scripting in RSS feed item links","id":"CVE-2026-104816"},"products":["misskey"],"published":"2026-10-13","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-10-13","vendors":["misskey-dev"]},"summary":"Unauthenticated attackers can exhaust resources and probe internal networks via the RSS fetching API due to missing rate limits and size restrictions.","url":"https://insights.sbomify.com/CVE-2026-104817/"}