# CVE-2026-46349: Mastodon: LD-Signature Bypass via JSON-LD Named-Graph Restructuring

> Attackers can spoof signed activities by restructuring JSON-LD graphs, bypassing Linked-Data Signature verification in Mastodon.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** BIT-mastodon-2026-46349, GHSA-chgx-jx3p-rf73

## What is CVE-2026-46349?

CVE-2026-46349 is a medium-severity vulnerability in mastodon, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mastodon is a free, open-source social network server based on ActivityPub. Prior to 4.5.10, 4.4.17, and 4.3.23, Mastodon's normalization of incoming activities signed with Linked-Data Signatures does not sufficiently protect the activities from a certain class of spoofing, allowing attackers to re-arrange a valid signed JSON-LD activity from a third-party actor to have it processed differently. This vulnerability is fixed in 4.5.10, 4.4.17, and 4.3.23.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-46349?

1 open source package ship an affected version, including mastodon.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mastodon` | Bitnami | From 4.5.0 | 4.5.10 |

## How do I fix CVE-2026-46349?

Upgrade mastodon to 4.5.10 or later.

## Is CVE-2026-46349 being exploited?

There is no known exploitation of CVE-2026-46349 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46349 and fix it if it is affected.

What it is: CVE-2026-46349 is a medium-severity vulnerability in mastodon, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46349 in the wild and no public exploit code.

Affected packages and fixed versions:
- mastodon (Bitnami): affected from 4.5.0; fixed in 4.5.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46349/ (Markdown: https://insights.sbomify.com/CVE-2026-46349/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46349
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46349
- OSV: https://osv.dev/vulnerability/CVE-2026-46349

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46349/
Summaries are generated and may contain mistakes; the official description above is the record.