Loading vulnerability…
The provided content describes an unauthenticated open redirect issue in Mastodon affecting versions prior to 4.5.8, 4.4.15, and 4.3.21. According to the content, the flaw exists in the /web/* route due to improper handling of URL-encoded path segments. Specifically, URL-encoded slashes such as %2F can bypass Rails path normalization and be interpreted as host-relative redirects, allowing an attacker to craft a specially encoded URL that redirects a victim to an arbitrary external domain. However, the same content also states that CVE-2026-33868 does not exist in NVD or any public vulnerability database and that the underlying issue is referenced by GitHub Security Advisory GHSA-xqw8-4j56-5hj6 rather than a valid public CVE assignment. Accordingly, the vulnerability details appear to describe a real Mastodon open redirect, but the CVE identifier in the content is not publicly validated.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
/web/* containing encoded path separators such as %2F, and consider adding reverse-proxy or WAF rules to reject malformed or double-encoded redirect-like paths. User-facing mitigations include warning users before leaving the site and monitoring for phishing campaigns abusing trusted Mastodon URLs. These are compensating controls only; patching is the definitive fix.Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.