This page was not yet optimized for use on mobile devices.
CVE-2025-49005
Data
| Vulnerability ID | CVE-2025-49005 |
|---|---|
| Published on | 03.07.2025 21:15 |
| Severity | LOW |
Vulnerable configurations
-
cpe:2.3:a:vercel:next.js:15.3.0:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary10:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary11:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary12:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary13:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary14:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary15:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.3.0:canary16:*:*:*:node.js:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.