Unauthenticated SSR data disclosure via path-keyed payload cache
Published Aug 5, 2026 · Updated Aug 5, 2026
Information disclosure in Nuxt 4.4.0 through 4.5.0 allows remote attackers to read another user's SSR payload via an HTTP request. The runtime renderer stores cache:nuxt:payload entries under path-only keys and returns them before route middleware or page guards run. Exploitation requires a cache, swr, or isr route with payload extraction and user-specific SSR data that another user has already warmed.
Summary
What happened
Information disclosure in Nuxt 4.4.0 through 4.5.0 allows remote attackers to read another user's SSR payload via an HTTP request. The runtime renderer stores cache:nuxt:payload entries under path-only keys and returns them before route middleware or page guards run. Exploitation requires a cache, swr, or isr route with payload extraction and user-specific SSR data that another user has already warmed.
The record
- CVE
- CVE-2026-71316
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- Nuxt
- Product
- Nuxt
- Classifications
- CWE-862, CWE-524, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 4.4.0, < 4.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo