# CVE-2025-62175: Mastodon streaming API fails to disconnect disabled and suspended users

> Disabled or suspended users can maintain streaming API connections to receive real-time updates, bypassing moderation controls.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** BIT-mastodon-2025-62175, GHSA-r2fh-jr9c-9pxh

## What is CVE-2025-62175?

CVE-2025-62175 is a medium-severity missing authorization vulnerability in mastodon, published on 13 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mastodon is a free, open-source social network server based on ActivityPub. In versions before 4.4.6, 4.3.14, and 4.2.27, disabling or suspending a user account does not disconnect the account from the streaming API. This allows disabled or suspended accounts to continue receiving real-time updates through existing streaming connections and to establish new streaming connections, even though they cannot interact with other API endpoints. This undermines moderation actions, as administrators expect disabled or suspended accounts to be fully disconnected from the service. This issue has been patched in versions 4.4.6, 4.3.14, and 4.2.27. No known workarounds exist.

Weakness: CWE-274 (Improper Handling of Insufficient Privileges), CWE-273 (Improper Check for Dropped Privileges)

## Which versions are affected by CVE-2025-62175?

1 open source package ship an affected version, including mastodon. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mastodon` | Bitnami | All versions | 4.2.27, 4.3.14, 4.4.6 |

Products: Joinmastodon Mastodon.

## How do I fix CVE-2025-62175?

Upgrade mastodon to a fixed version for your release line: 4.2.27, 4.3.14 or 4.4.6.

## Is CVE-2025-62175 being exploited?

There is no known exploitation of CVE-2025-62175 in the wild and no public exploit code.

## Other vulnerabilities in mastodon

- [CVE-2023-36460](https://insights.sbomify.com/CVE-2023-36460/): Mastodon vulnerable to arbitrary file creation through media attachments (critical 10.0)
- [CVE-2022-2166](https://insights.sbomify.com/CVE-2022-2166/): Improper Restriction of Excessive Authentication Attempts in mastodon/mastodon (critical 9.8)
- [CVE-2022-24307](https://insights.sbomify.com/CVE-2022-24307/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-21018](https://insights.sbomify.com/CVE-2018-21018/): Auth bypass in n/a (critical 9.8)
- [CVE-2024-23832](https://insights.sbomify.com/CVE-2024-23832/): Mastodon Remote user impersonation and takeover (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62175 and fix it if it is affected.

What it is: CVE-2025-62175 is a medium-severity missing authorization vulnerability in mastodon, published on 13 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62175 in the wild and no public exploit code.

Affected packages and fixed versions:
- mastodon (Bitnami): affected all versions; fixed in 4.2.27, 4.3.14, 4.4.6

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62175/ (Markdown: https://insights.sbomify.com/CVE-2025-62175/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62175
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62175
- OSV: https://osv.dev/vulnerability/CVE-2025-62175

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62175/
Summaries are generated and may contain mistakes; the official description above is the record.