This page was not yet optimized for use on mobile devices.
CVE-2026-41516
Data
| Vulnerability ID | CVE-2026-41516 |
|---|---|
| Published on | 06.07.2026 20:16 |
| Severity | LOW |
Vulnerable configurations
-
cpe:2.3:o:trustedfirmware:op-tee:4.5.0:-:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.5.0:rc1:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.6.0:-:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.6.0:rc1:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.7.0:-:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.7.0:rc1:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.8.0:-:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.8.0:rc1:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.9.0:-:*:*:*:*:*:*,
cpe:2.3:o:trustedfirmware:op-tee:4.9.0:rc1:*:*:*:*:*:*,
…
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.