This page was not yet optimized for use on mobile devices.
CVE-2026-45772
Data
| Vulnerability ID | CVE-2026-45772 |
|---|---|
| Published on | 15.05.2026 16:16 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:vercel:turborepo:1.1.0:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.0:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.0:canary2:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.0:canary3:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.3:-:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.3:canary0:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.3:canary1:*:*:*:node.js:*:*,
cpe:2.3:a:vercel:turborepo:1.1.3:canary2:*:*:*: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.