Read the docs

Client IP spoofing in Mastodon lets attackers bypass blocks and rate limits

Priority MEDIUM 44Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · None · Low
Fix status
No fix listed

Attack profile from CVSS 3.1 · GHSA-qp4r-p842-mw5c. Fix status from GitHub.

Summary

Mastodon's recommended nginx.conf allowed clients to set an HTTP request header to arbitrary values, and Mastodon trusted that header as the client's IP address. An unauthenticated remote attacker can spoof their IP address to bypass IP blocks and some built-in rate limits.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Summary The recommended `nginx.conf` configuration file allowed clients to set a HTTP request header to arbitrarily values, which would then be used by Mastodon as a source of truth for the client's IP address. ### Impact By spoofing their IP address, an attacker can bypass IP blocks and some of Mastodon's built-in rate-limits.

Why it matters now

Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—mastodon<= 4.7.4—No fix listedGHSA-qp4r-p842-mw5c
  • mastodon Vendor— Affected <= 4.7.4 Fixed in — No fix listed GHSA-qp4r-p842-mw5c

Remediation

The sources list no fixed version for mastodon.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Timeline

  1. 2026-11-12 Threatist record created from GHSA-qp4r-p842-mw5c

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences