How severe is CVE-2025-60250?

CVE-2025-60250 has a CVSS 3.x base score of 4.7, rated medium severity. It is exploitable over an adjacent network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2025-60250 being actively exploited?

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

How do I fix CVE-2025-60250?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-60250 have an EU (EUVD) identifier?

Yes. CVE-2025-60250 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-31182.

When was CVE-2025-60250 published?

CVE-2025-60250 was published on 2025-09-26 and last updated on 2026-06-17.

CVE-2025-60250

CVE-2025-60250 is a medium-severity vulnerability with a CVSS 3.x base score of 4.7. 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: Medium (CVSS 3.x base score 4.7)
EPSS exploit prediction: 0% (7th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-31182
Weakness: CWE-321
Published: 2025-09-26
Last modified: 2026-06-17

Description

Unitree Go2, G1, H1, and B2 devices through 2025-09-20 decrypt BLE packet data by using the df98b715d5c6ed2b25817b6f2554124a key and the 2841ae97419c2973296a0d4bdfe19a4f IV.

Frequently asked questions

What is CVE-2025-60250?: Unitree Go2, G1, H1, and B2 devices through 2025-09-20 decrypt BLE packet data by using the df98b715d5c6ed2b25817b6f2554124a key and the 2841ae97419c2973296a0d4bdfe19a4f IV.
How severe is CVE-2025-60250?: CVE-2025-60250 has a CVSS 3.x base score of 4.7, rated medium severity. It is exploitable over an adjacent network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2025-60250 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (7th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-60250?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-60250 have an EU (EUVD) identifier?: Yes. CVE-2025-60250 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-31182.
When was CVE-2025-60250 published?: CVE-2025-60250 was published on 2025-09-26 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-2026-32644 — Critical (CVSS 9.8): Specific firmware versions of Milesight AIOT cameras use SSL certificates with default private keys.
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…

Browse all CWE-321 vulnerabilities →