Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-71316 – SSR Payload Cache Data Disclosure / Missing Authorization – Nuxt 4.4.0 through 4.5.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-71316 is a sensitive-information cache disclosure and missing-authorization vulnerability in the Nuxt web framework. Nuxt’s runtime payload cache returns cached server-side rendered (SSR) payloads before route middleware and page guards execute, allowing unauthenticated network clients to receive SSR data cached for other users. It affects Nuxt 4.4.0 through 4.5.0 and carries a CVSS v3.1 base score of 7.5 (High).

Technical details

  • Root cause: The renderer stored SSR payloads in shared cache storage keyed only on the page path, omitting authentication dimensions such as cookies or authorization headers. Route middleware and page guards ran after the cached entry was returned rather than before, due to unenforced import.meta.prerender checks (CWE-524: Use of Cache Containing Sensitive Information; CWE-862: Missing Authorization).
  • Trigger conditions: An authenticated user accesses a protected page whose SSR payload is then cached.
  • Attack vector: Network. A different user or unauthenticated client requests the cached payload endpoint (/<page>/_payload.json) and receives the first user’s cached SSR data. No privileges, authentication, or user interaction are required.
  • Impact: Unauthorized disclosure of another user’s server-side rendered data, potentially including API responses, profile data, and other sensitive information. Confidentiality impact is high; integrity and availability are not affected.

Affected software

  • Nuxt 4.4.0 through 4.5.0 (inclusive)
  • Nuxt 3.x and 5.x are not affected (they retained the import.meta.prerender gates)

Severity

  • CVSS v3.1 base score: 7.5 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Nuxt 4.5.1, which contains the fix.
  • If no patch can be applied:
    • Disable payload extraction by setting experimental.payloadExtraction: false.
    • Avoid caching authenticated pages that contain user-specific SSR data.
    • Restrict access to /**/_payload.json at the CDN or reverse-proxy layer.
    • Purge any existing cached payloads from CDN infrastructure.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: <div id="__nuxt", window.__NUXT__
  • URL of a loaded script: /_nuxt/
  • JavaScript object present once the page runs: $nuxt

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge