CVE-2025-58309

CVE-2025-58309 is a medium-severity vulnerability in Huawei Harmonyos with a CVSS 3.x base score of 6.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-264.

Key facts

Description

Permission control vulnerability in the startup recovery module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality.

Frequently asked questions

What is CVE-2025-58309?
Permission control vulnerability in the startup recovery module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality.
How severe is CVE-2025-58309?
CVE-2025-58309 has a CVSS 3.x base score of 6.8, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability high.
Is CVE-2025-58309 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-58309?
CVE-2025-58309 primarily affects Huawei Harmonyos. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-58309?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-58309 have an EU (EUVD) identifier?
Yes. CVE-2025-58309 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-199848.
When was CVE-2025-58309 published?
CVE-2025-58309 was published on 2025-11-28 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Huawei Harmonyos

All CVEs affecting Huawei Harmonyos →

Other CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities

Browse all CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities →