Skip to main content
CVE-2026-46349VulnerabilityPublished

BIT-mastodon-2026-46349: Mastodon: LD-Signature Bypass via JSON-LD Named-Graph Restructuring

Affects mastodonSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 4.5.10 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

Severity
Medium

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

EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.5.10

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 16 Nov 2026.

What to do

Upgrade mastodon to 4.5.10.

Affected software

ProductAffectedFixed in
Bitnamimastodonpkg:bitnami/mastodonOther threatsAffected
  • >=4.5.0 <4.5.10
Fixed in
  • 4.5.10

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.5.10 or later, or to 4.4.17 or later, or to 4.3.23 or later, as these versions contain the fix for this vulnerability. No other mitigation is indicated.

Description

Mastodon versions prior to 4.5.10, 4.4.17, and 4.3.23 have a vulnerability in the normalization of incoming activities signed with Linked-Data Signatures. This flaw allows attackers to rearrange a valid signed JSON-LD activity from a third party so that it is processed differently, potentially bypassing signature validation. The issue is fixed in versions 4.5.10, 4.4.17, and 4.3.23.

References

Community reviews

Loading reviews…