CVE-2026-72916 mastodon CVE debrief

Who should care

Defenders of Mastodon instances, especially those with private resources and services that could be accessed through loopback interfaces, should assess exposure and apply patches. Defenders should prioritize verifying exposure and applying patches to Mastodon instances, especially those with private resources and services that could be accessed through loopback interfaces.

Why it matters

CVE-2026-72916 is a vulnerability in Mastodon that allows an attacker to bypass private address checks and access private resources. Defenders should prioritize verifying exposure and applying patches.

• Potential access to private resources and services through loopback interfaces
• Bypass of ALLOWED_PRIVATE_ADDRESSES protection
• Possible exploitation requires a system supporting the obsolete IPv4-compatible IPv6 mechanism

Technical summary

The PrivateAddressCheck.private_address? in app/lib/private_address_check.rb normalized IPv4-mapped IPv6 addresses but did not recognize IPv4-compatible IPv6 addresses with IPAddr#ipv4_compat?. An attacker could supply an address in the omitted range to bypass the ALLOWED_PRIVATE_ADDRESSES protection and make Mastodon send HTTP requests to loopback interfaces, potentially accessing private resources and services. Exploitation requires a system that supports the obsolete IPv4-compatible IPv6 mechanism. This issue is fixed in versions 4.4.21, 4.5.14, 4.6.4, and 4.7.0-beta.1.

Defensive priority

Defenders should prioritize verifying exposure and applying patches to Mastodon instances, especially those with private resources and services that could be accessed through loopback interfaces.

Recommended defensive actions

• Verify Mastodon instance version and apply patches to 4.4.21, 4.5.14, 4.6.4, or 4.7.0-beta.1 if necessary
• Review ALLOWED_PRIVATE_ADDRESSES configuration and update as needed
• Monitor Mastodon instance for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source references provide details on the vulnerability, its impact, and the fixed versions. However, the corpus does not establish versions, exploitation, impact, or remediation for all deployment contexts, requiring verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.