This page was not yet optimized for use on mobile devices.
CVE-2026-0519
Vulnerable configurations
-
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:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.54:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.55:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:13.56:*:*:*:*:*:*:*,
cpe:2.3:a:absolute:secure_access:14.02:*:*:*:*:*:*:*,
…
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.