LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22245: Mastodon has SSRF Protection bypass

Mastodon is a free, open-source social network server based on ActivityPub. By nature, Mastodon performs a lot of outbound requests to user-provided domains. Mastodon, however, has some protection mechanism to disallow requests to local IP addresses (unless specified in `ALLOWED_PRIVATE_ADDRESSES`) to avoid the "confused deputy" problem. The list of disallowed IP address ranges was lacking some IP address ranges that can be used to reach local IP addresses. An attacker can use an IP address in the affected ranges to make Mastodon perform HTTP requests against loopback or local network hosts, potentially allowing access to otherwise private resources and services. This is fixed in Mastodon v4.5.4, v4.4.11, v4.3.17 and v4.2.29.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22245 lets a logged-in attacker bypass Mastodon’s server-side request forgery protections. Mastodon may be tricked into making HTTP requests to loopback or local network systems that should not be reachable externally. Business urgency is highest for organizations running their own Mastodon servers, especially where internal services are reachable from the Mastodon host.

Executive priority

Treat as a high-priority patch for any self-hosted Mastodon environment. The main business risk is internal system exposure through a public-facing social server. If Mastodon has broad internal network reach, accelerate remediation and network review. If no Mastodon is deployed, no direct exposure is indicated by the provided sources.

Technical view

Mastodon’s private-address blocking missed certain IP ranges usable to reach local or loopback addresses. This is CWE-918 SSRF. Affected versions are before 4.2.29, 4.3 beta through before 4.3.17, 4.4 beta through before 4.4.11, and 4.5 beta through before 4.5.4. CVSS v4.0 score is 7.1, with low attack complexity and low privileges required.

Likely exposure

Exposure is limited to Mastodon deployments running affected versions. Risk depends on what the Mastodon server can reach on loopback or internal networks, including metadata endpoints, admin panels, databases, or other private HTTP services. Internet-facing Mastodon instances are the primary concern because they routinely process user-controlled remote content and domains.

Exploitation context

Sources state an attacker with low privileges can cause Mastodon to send HTTP requests to local or private network hosts. No source in the bundle reports active exploitation, and the CVE is not marked in KEV. The advisory indicates integrity impact rather than confidentiality or availability in the supplied CVSS vector.

Researcher notes

The public description identifies an incomplete disallowed-IP range list in Mastodon’s SSRF protections. Fixed releases and commits are referenced, but the bundle does not provide proof-of-concept details or exploitation telemetry. Validation should focus on version state, reachable internal services from the Mastodon host, and whether ALLOWED_PRIVATE_ADDRESSES is intentionally configured.

Mitigation direction

  • Upgrade Mastodon to 4.5.4, 4.4.11, 4.3.17, or 4.2.29 as applicable.
  • Prioritize internet-facing Mastodon servers and instances with access to sensitive internal services.
  • Review Mastodon vendor advisory and release notes before applying updates.
  • Restrict network access from Mastodon hosts to unnecessary internal HTTP services where feasible.

Validation and detection

  • Inventory all Mastodon instances and record exact running versions.
  • Confirm versions are not in the affected ranges listed by the advisory.
  • Verify upgraded instances report a fixed Mastodon version.
  • Review egress controls from Mastodon hosts to loopback and internal networks.
  • Check application logs for unusual outbound requests to private or loopback addresses.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22245 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

7.1High
CVSS 4.0 vector shape for CVE-2026-22245Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mastodonmastodon< 4.2.29, >= 4.3.0-beta.1, < 4.3.17, >= 4.4.0-beta.1, < 4.4.11, >= 4.5.0-beta.1, < 4.5.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.