Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Stored XSS in Next.js App Router CSP nonce parsing

IdentifiersCVE-2026-44581CWE-79· Improper Neutralization of Input…

CVE-2026-44581 affects Next.js App Router applications in versions 13.4.0 through before 15.5.16 and 16.2.5 when those applications rely on CSP nonces and are deployed behind shared caches. In affected versions, malformed nonce values derived from request headers can be reflected into rendered HTML without sufficient sanitization. This creates an unsafe HTML injection condition in nonce handling, allowing an attacker to poison a cache with a maliciously crafted response. Subsequent users served the poisoned cached response can then execute attacker-controlled script in their browsers. The issue is described as a CSP nonce parsing edge case and results in stored cross-site scripting via cache poisoning.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables stored cross-site scripting against later visitors who receive the poisoned cached response. This can lead to execution of attacker-controlled JavaScript in victims' browsers, including session theft, DOM manipulation, credential or token exfiltration, phishing overlays, and other actions available in the application's origin context. Because the attack relies on shared cache poisoning, a single malicious request may impact multiple subsequent users.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, strip inbound Content-Security-Policy-related request headers from untrusted traffic so malformed nonce values cannot be propagated into rendered HTML. Additionally, reduce or disable caching for affected dynamic responses, especially where nonce-bearing HTML may be cached by shared intermediaries, and purge shared caches to remove any poisoned entries.

Remediation

Patch, then assume compromise.

Upgrade Next.js to a fixed version. The vulnerability is fixed in 15.5.16 and 16.2.5. Fixed releases reject or safely handle malformed nonce values and apply stricter nonce sanitization in the rendering path. Deploy the patched version across all affected environments and purge any shared caches after upgrading to remove potentially poisoned responses.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
VercelNextapplication
VercelNext.Jsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.