This page was not yet optimized for use on mobile devices.
CVE-2026-35213
Data
| Vulnerability ID | CVE-2026-35213 |
|---|---|
| Published on | 06.04.2026 21:16 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:content_project:content:1.0.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:1.0.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:1.0.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:2.0.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:3.0.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:3.0.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:3.0.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:3.0.3:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:3.0.4:*:*:*:*:node.js:*:*,
cpe:2.3:a:content_project:content:3.0.5:*:*:*:*: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.