This page was not yet optimized for use on mobile devices.
CVE-2026-41511
Data
| Vulnerability ID | CVE-2026-41511 |
|---|---|
| Published on | 08.05.2026 19:16 |
| Severity | MEDIUM |
Vulnerable configurations
-
cpe:2.3:a:openmcdf:openmcdf:1.4.2:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:1.5.0:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:1.5.3:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:1.5.3.1:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:1.5.3.2:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:1.5.3.3:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:1.5.4:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:1.5.5:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:2.1.1.29598:*:*:*:*:*:*:*,
cpe:2.3:a:openmcdf:openmcdf:2.1.2.1274:*:*:*:*:*:*:*,
…
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.