Skip to main content
CVE-2026-50129VulnerabilityPublished

BIT-mastodon-2026-50129: Mastodon: Persistent anonymous DoS via unhandled NoMethodError in MATH_TRANSFORMER

Affects mastodonSource GCVE Database

0
Compare

Not known to be exploited · fixed in 4.5.11 : patch mastodon soon.

Data as of 18 Nov 2026, 20:25 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.5.11, 4.4.18, 4.3.24

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 18 Nov 2026.

What to do

Upgrade mastodon to 4.5.11, 4.4.18 or 4.3.24.

Affected software

ProductAffectedFixed in
Bitnamimastodonpkg:bitnami/mastodonOther threatsAffected
  • <4.3.24
  • >=4.4.0 <4.4.18
  • >=4.5.0 <4.5.11
Fixed in
  • 4.3.24
  • 4.4.18
  • 4.5.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Mastodon to version 4.3.24, 4.4.18, or 4.5.11 or later, where this vulnerability is fixed. No other mitigation is indicated as the issue is resolved by these official patches.

Description

Mastodon versions prior to 4.3.24, 4.4.18, and 4.5.11 contain a vulnerability where malformed <math> nodes cause an unhandled NoMethodError exception in the math sanitizer. This results in a persistent denial-of-service (DoS) condition affecting the entire server or specific user services depending on the context of the malformed input. The issue is fixed in versions 4.3.24, 4.4.18, and 4.5.11.

References

Community reviews

Loading reviews…