This page was not yet optimized for use on mobile devices.
CVE-2026-40035
Data
| Vulnerability ID | CVE-2026-40035 |
|---|---|
| Published on | 08.04.2026 22:16 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:ryandfir:unfurl:2020.08.12:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2020.11.02:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2021.03.11:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2021.06.15:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2022.02:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2022.11:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2022.11.01:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2023.09:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2023.09.01:*:*:*:*:*:*:*,
cpe:2.3:a:ryandfir:unfurl:2023.09.02:*:*:*:*:*:*:*,
…
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.