CVE intelligence and bounded remediation
CVE-2026-27477 — Mastodon is a free, open-source social network server based on ActivityPub
Mastodon is a free, open-source social network server based on ActivityPub. FASP registration requires manual approval by an administrator. In versions 4.4.0 through 4.4.13 and 4.5.0 through 4.5.6, an unauthenticated attacker can register a FASP with an attacker-chosen `base_url` that includes or resolves to a local / internal address, leading to the Mastodon server making requests to that address. This only affects Mastodon servers that have opted in to testing the experimental FASP feature by setting the environment variable `EXPERIMENTAL_FEATURES` to a value including `fasp`. An attacker can force the Mastodon server to make http(s) requests to internal systems. While they cannot control the full URL that is being requested (only the prefix) and cannot see the result of those requests, vulnerabilities or other undesired behavior could be triggered in those systems. The fix is included in the 4.4.14 and 4.5.7 releases. Admins that are actively testing the experimental "fasp" feature should update their systems. Servers not using the experimental feature flag `fasp` are not affected.
- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Published
- 2026-02-24
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-918
Affected products
- joinmastodon / mastodon
Matched remediation archetype
Server-side request forgery and unintended proxying
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory server-side URL fetchers, webhooks, importers, previews, redirects, proxies, and protocol handlers reachable from untrusted input.
- Map egress paths to internal services, metadata endpoints, loopback, private address space, and privileged control planes.
- Review DNS resolution, redirect, proxy, credential-forwarding, and URL parsing behavior without requesting sensitive targets.
Remediate safely
- Replace arbitrary destinations with named integrations or a strict allowlist of schemes, hosts, ports, and paths.
- Resolve and validate every destination and redirect hop, then enforce egress policy independently of application checks.
- Remove ambient credentials and sensitive headers from fetchers; apply response size, time, and content limits.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.