CVE-2024-34535: mastodon · n/a
Affects mastodonSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmastodon/mastodonpkg:github/mastodon/mastodonOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately review their Mastodon 4.1.6 deployments and monitor API usage logs for unusual patterns indicative of rate limit bypass attempts, such as spikes in requests from single IP addresses or unusual header values. Implementing additional custom rate limiting or request validation at the web server or API gateway level can provide a temporary control. Network-level controls such as WAF (Web Application Firewall) rules can be configured to detect and block suspicious header manipulations. Administrators should stay alert for official patches or updates from Mastodon developers addressing this vulnerability and apply them promptly once available. Additionally, consider restricting API access to authenticated and trusted clients where feasible, and conduct regular security assessments of API endpoints. Educating developers and administrators about this vulnerability and the importance of validating all request headers can help prevent similar issues in the future.
Description
In Mastodon 4.1.6, API endpoint rate limiting can be bypassed by setting a crafted HTTP request header.