CVE-2026-44575 is an authorization bypass vulnerability in Next.js App Router applications that rely on middleware or proxy-based access-control checks. Affected versions generate middleware matchers that cover canonical routes but fail to consistently match certain App Router transport-specific request variants used for React Server Components and segment prefetching. As a result, specially crafted alternate route forms, including .rsc and segment-prefetch variants, can resolve to the same protected page while bypassing the intended middleware authorization logic. The flaw has been attributed to incomplete middleware matcher regex generation in the Next.js routing and build analysis logic. When the alternate transport URL is requested, middleware execution can be skipped and the protected page is still rendered, returning the React Server Components payload for content that should have required authorization.
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.
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.
11 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.