Skip to main content
CVE-2026-46348VulnerabilityPublished

BIT-mastodon-2026-46348: Mastodon: SSRF Bypass via IPv6 Unspecified Address (::)

Affects mastodonSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 4.5.10 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 35% 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 18 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 4.4.17, 4.3.23 or later for those branches) where this vulnerability is fixed. Patch availability is confirmed by the vendor's versioning information. No additional mitigation is required once upgraded.

Description

Mastodon versions prior to 4.5.10, 4.4.17, and 4.3.23 have an SSRF vulnerability due to incomplete filtering of IP address ranges. Attackers can exploit this by using IPv6 unspecified addresses (::) to bypass restrictions and make HTTP requests to local loopback interfaces, potentially accessing private resources. This issue is fixed in versions 4.5.10, 4.4.17, and 4.3.23.

References

Community reviews

Loading reviews…