This page was not yet optimized for use on mobile devices.
CVE-2025-49826
Data
| Vulnerability ID | CVE-2025-49826 |
|---|---|
| Published on | 03.07.2025 21:15 |
| Severity | HIGH |
Vulnerable configurations
- cpe:2.3:a:vercel:next.js:15.0.4:canary51:*:*:*:node.js:*:*
- cpe:2.3:a:vercel:next.js:15.0.4:canary52:*:*:*:node.js:*:*
-
cpe:2.3:a:vercel:next.js:15.1.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.1.1:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.1.1:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.1.1:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.1.1:canary10:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.1.1:canary11:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.1.1:canary12:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:15.1.1:canary13:*:*:*: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.