Vulnerability in Mastodon (CVE-2026-48028)
Summary
Vulnerability in Mastodon (CVE-2026-48028). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.5.10 or later.
Original description
The description as published by the source.
Mastodon is a free, open-source social network server based on ActivityPub. Prior to 4.5.10, 4.4.17, and 4.3.23, Mastodon's normalization of incoming activities signed with Linked-Data Signatures does not sufficiently protect the activities from a certain class of spoofing, allowing threat actors to remove JSON entries from valid signed activities from a third-party actor. This vulnerability is fixed in 4.5.10, 4.4.17, and 4.3.23.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48028 has been found in Mastodon.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade Mastodon to 4.5.10 or later.
If unsure, ask your IT team or search "Mastodon CVE-2026-48028" on the vendor's site.
CVE-2026-48028 (Mastodon) — CWE-354 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.5.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-354) exists in Mastodon.
Check the vendor advisory for the affected versions of Mastodon.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 4.5.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Mastodon' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Mastodon' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Mastodonを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Mastodon to 4.5.10ステージング環境で 4.5.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。