Skip to main content
VulnerabilityPublished Updated

CVE-2025-52662: Vercel Nuxt Devtools · Cross-site Scripting

Affects Vercel Nuxt DevtoolsSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubnuxt/devtoolspkg:github/nuxt/devtoolsOther threatsAffected
  • =2.6.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade Nuxt DevTools to version 2.6.4 or later immediately to apply the official patch addressing the XSS vulnerability.
  2. Restrict access to Nuxt DevTools interfaces to trusted internal networks and authenticated users only, minimizing exposure to untrusted or external users.
  3. Implement Content Security Policy (CSP) headers to reduce the risk of XSS exploitation by restricting the sources of executable scripts.
  4. Conduct regular code reviews and security testing of development tools and environments to detect and remediate similar vulnerabilities early.
  5. Monitor logs and network traffic for unusual activities indicative of token theft or unauthorized access attempts.
  6. Educate developers and users about the risks of clicking on untrusted links or interacting with suspicious content while using development tools.
  7. Consider implementing token expiration and rotation policies to limit the window of opportunity for attackers if tokens are compromised.
  8. Use multi-factor authentication (MFA) where possible to add an additional layer of security beyond token-based authentication.

Description

A vulnerability in Nuxt DevTools has been fixed in version **2.6.4***. This issue may have allowed Nuxt auth token extraction via XSS under certain configurations. All users are encouraged to upgrade. More details: https://vercel.com/changelog/cve-2025-52662-xss-on-nuxt-devtools

References

Community reviews

Loading reviews…