This page was not yet optimized for use on mobile devices.
CVE-2026-32711
Data
| Vulnerability ID | CVE-2026-32711 |
|---|---|
| Published on | 20.03.2026 02:16 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:pydicom:pydicom:2.0.0:-:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.0.0:rc1:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.1.0:*:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.1.1:*:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.1.2:*:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.2.0:-:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.2.0:rc1:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.2.1:*:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.2.2:*:*:*:*:python:*:*,
cpe:2.3:a:pydicom:pydicom:2.3.0:*:*:*:*:python:*:*,
…
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.