{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-28432 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-28432 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-28432 is a high-severity vulnerability in misskey-dev misskey, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-28432 and fix it if it is affected.\n\nWhat it is: CVE-2026-28432 is a high-severity vulnerability in misskey-dev misskey, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-28432 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-28432/ (Markdown: https://insights.sbomify.com/CVE-2026-28432/index.md)","id":"CVE-2026-28432","markdown":"https://insights.sbomify.com/CVE-2026-28432/index.md","name":"CVE-2026-28432","record":{"aliases":["GHSA-grwc-c762-gcvp"],"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":"Attackers can bypass HTTP signature verification in Misskey, potentially impersonating federated entities or bypassing security checks.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"misskey","vendor":"misskey"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Misskey is an open source, federated social media platform. All Misskey servers prior to 2026.3.1 contain a vulnerability that allows bypassing HTTP signature verification. Although this is a vulnerability related to federation, it affects all servers regardless of whether federation is enabled or disabled. This vulnerability is fixed in 2026.3.1.","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":"HTTP signature verification can be bypassed","id":"CVE-2026-28432","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Misskey lacks resource ownership validation","id":"CVE-2026-28433"},"packages":[],"prev":{"headline":"Misskey lacks proper authorization checks and input validation","id":"CVE-2026-28431"},"products":["misskey"],"published":"2026-03-09","related":[{"cvss_score":9.3,"headline":"Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes","id":"CVE-2025-25306","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":9.3,"headline":"Misskey's missing signature validation allows arbitrary users to impersonate any remote user.","id":"CVE-2023-49079","kev_date_added":null,"published":"2023-11-29"},{"cvss_score":9.2,"headline":"Misskey lacks proper authorization checks and input validation","id":"CVE-2026-28431","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.1,"headline":"Misskey vulnerable to improper authorization when accessing with third-party application","id":"CVE-2023-52139","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles in Misskey","id":"CVE-2024-52590","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles and notes in Misskey","id":"CVE-2024-52591","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":8.8,"headline":"SQL injection of notes/search-by-tag","id":"CVE-2023-24812","kev_date_added":null,"published":"2023-02-22"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-03-10","vendors":["misskey-dev"]},"summary":"Attackers can bypass HTTP signature verification in Misskey, potentially impersonating federated entities or bypassing security checks.","url":"https://insights.sbomify.com/CVE-2026-28432/"}