This page was not yet optimized for use on mobile devices.
CVE-2026-34875
Data
| Vulnerability ID | CVE-2026-34875 |
|---|---|
| Published on | 01.04.2026 18:16 |
| Severity | CRITICAL |
Vulnerable configurations
- cpe:2.3:a:arm:mbed_tls:3.5.0:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.5.1:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.5.2:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.6.0:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.6.1:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.6.2:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.6.3:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.6.4:*:*:*:*:*:*:*, cpe:2.3:a:arm:mbed_tls:3.6.5:*:*:*:*:*:*:*
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.