This page was not yet optimized for use on mobile devices.
CVE-2025-55173
Data
| Vulnerability ID | CVE-2025-55173 |
|---|---|
| Published on | 29.08.2025 22:15 |
| Severity | MEDIUM |
Vulnerable configurations
-
cpe:2.3:a:vercel:next.js:1.0.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.0.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.0.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.1.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.1.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.1.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.2.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.2.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.2.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:next.js:1.2.3:*:*:*:*: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.