This page was not yet optimized for use on mobile devices.
CVE-2026-64608
Data
| Vulnerability ID | CVE-2026-64608 |
|---|---|
| Published on | 21.07.2026 10:16 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:apache:fory:0.14.0:-:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.14.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.14.1:-:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.14.1:rc1:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.15.0:-:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.15.0:rc1:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.15.0:rc2:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.15.0:rc3:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.16.0:-:*:*:*:*:*:*,
cpe:2.3:a:apache:fory:0.16.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.