How severe is CVE-2026-32644?

CVE-2026-32644 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-32644 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (12th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-32644?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-32644 have an EU (EUVD) identifier?

Yes. CVE-2026-32644 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25957.

When was CVE-2026-32644 published?

CVE-2026-32644 was published on 2026-04-28 and last updated on 2026-06-17.

CVE-2026-32644

CVE-2026-32644 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v4: 9.2
EPSS exploit prediction: 0% (12th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-25957
Weakness: CWE-321
Published: 2026-04-28
Last modified: 2026-06-17

Description

Specific firmware versions of Milesight AIOT cameras use SSL certificates with default private keys.

Frequently asked questions

What is CVE-2026-32644?: Specific firmware versions of Milesight AIOT cameras use SSL certificates with default private keys.
How severe is CVE-2026-32644?: CVE-2026-32644 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-32644 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (12th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-32644?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-32644 have an EU (EUVD) identifier?: Yes. CVE-2026-32644 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25957.
When was CVE-2026-32644 published?: CVE-2026-32644 was published on 2026-04-28 and last updated on 2026-06-17.

References

Other CWE-321 vulnerabilities

CVE-2024-30207 — Critical (CVSS 10.0): A vulnerability has been identified in SIMATIC RTLS Locating Manager (6GT2780-0DA00) (All versions < V3.0.1.1), SIMATIC…
CVE-2014-5419 — Critical (CVSS 10.0): GE Multilink ML800, ML1200, ML1600, and ML2400 switches with firmware 4.2.1 and earlier and Multilink ML810, ML3000,…
CVE-2024-35344 — Critical (CVSS 9.9): Certain Anpviz products contain a hardcoded cryptographic key stored in the firmware of the device. This affects…
CVE-2026-28742 — Critical (CVSS 9.8): Naxclow devices use a uniform request-signing scheme based on a hard-coded, platform-wide salt embedded in every…
CVE-2025-67112 — Critical (CVSS 9.8): Use of a hard-coded AES-256-CBC key in the configuration backup/restore implementation of Small Cell Sercomm SCE4255W…
CVE-2025-67305 — Critical (CVSS 9.8): In RUCKUS Network Director (RND) < 4.5.0.56, the OVA appliance contains hardcoded SSH keys for the postgres user. These…

Browse all CWE-321 vulnerabilities →