# CVE-2025-62605: Mastodon quotes control can be bypassed

> Attackers can bypass quote controls by quoting their own reblogs, gaining unauthorized access to post previews and affordances.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 21 Oct 2025
- **Updated:** 21 Oct 2025
- **Also known as:** BIT-mastodon-2025-62605, GHSA-8h43-rcqj-wpc6

## What is CVE-2025-62605?

CVE-2025-62605 is a medium-severity vulnerability in mastodon, published on 21 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 Mastodon version 4.4, support for verifiable quote posts with quote controls was added, but it is possible for an attacker to bypass these controls in Mastodon versions prior to 4.4.8 and 4.5.0-beta.2. Mastodon internally treats reblogs as statuses. Since they were not special-treated, an attacker could reblog any post, then quote their reblog, technically quoting themselves, but having the quote feature a preview of the post they did not get authorization for with all of the affordances that would be otherwise denied by the quote controls. This issue has been patched in versions 4.4.8 and 4.5.0-beta.2.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mastodon` | Bitnami | From 4.4.0 | 4.4.8 |

Products: Joinmastodon Mastodon.

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

Upgrade mastodon to 4.4.8 or later.

## Is CVE-2025-62605 being exploited?

There is no known exploitation of CVE-2025-62605 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-62605 and fix it if it is affected.

What it is: CVE-2025-62605 is a medium-severity vulnerability in mastodon, published on 21 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-62605 in the wild and no public exploit code.

Affected packages and fixed versions:
- mastodon (Bitnami): affected from 4.4.0; fixed in 4.4.8

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-62605/ (Markdown: https://insights.sbomify.com/CVE-2025-62605/index.md)
```

## Sources

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

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