This page was not yet optimized for use on mobile devices.
CVE-2026-33452
Data
| Vulnerability ID | CVE-2026-33452 |
|---|---|
| Published on | 30.04.2026 21:16 |
| Severity | MEDIUM |
Vulnerable configurations
-
cpe:2.3:a:absolute:secure_access:-:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:9.0:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:12.00:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:12.50:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:12.70:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.04:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.05:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.06:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.07:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.08:*:*:*:*:*:*:*,
…
running on/with
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.