This page was not yet optimized for use on mobile devices.
CVE-2026-64646
Data
| Vulnerability ID | CVE-2026-64646 |
|---|---|
| Published on | 27.07.2026 19:17 |
| Severity | MEDIUM |
Vulnerable configurations
-
cpe:2.3:a:vercel:next.js:13.0.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.1:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.1:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.1:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.1:canary2:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.1:canary3:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.1:canary4:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.2:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.2:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:13.0.2:canary1:*:*:*: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.