Huawei HarmonyOS CVE-2025-58283

Requires local access with at least low-level privileges on the device (CVSS PR:L) - realistically a malicious, trojanized, or compromised application already running on a HarmonyOS 5.0.1 or 5.1.0 device; there is no remote/network path (AV:L) and no user interaction is needed once the hostile app is present (UI:N). The vulnerability is in the Wi-Fi module's permission control, so exploitation depends on the device having that module active, and impact is limited to disclosure of confidential service data (C:H) with no modification (I:N) or disruption (A:N). Limiting factors for defenders: the attacker must first achieve local code execution, so this is a privilege/post-compromise amplifier rather than an initial-access flaw, and only Huawei HarmonyOS 5.0.1/5.1.0 builds are in scope.

This is a moderate, locally-scoped information-disclosure issue rather than a high-priority emergency. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 5.5 Medium) shows the attacker must already have local access with low privileges (PR:L) - e.g. a malicious or compromised app running on the device - and gains only confidentiality impact (C:H) with no integrity or availability effect. All exploitation signals point low and consistent: EPSS is 0.10% (1st percentile), the CVE is NOT on CISA KEV, and no public exploit code is referenced. There is no network vector and no scope change, so this is not a wormable or remotely-triggerable flaw. One notable tension: the input Tags label this 'Privilege Escalation', but the CVSS impact set (C:H/I:N/A:N) and the vendor description ('may affect service confidentiality') describe information disclosure, not a gain of elevated execution privileges - treat the privilege-escalation framing with caution and verify against the Huawei bulletin. Net: a real but low-urgency mobile-OS defect best addressed via normal patch cycles, not emergency response.

A malicious or trojanized application installed on a HarmonyOS 5.0.1/5.1.0 device abuses weak permission control in the Wi-Fi module to read confidential Wi-Fi-related data it should not have access to (e.g. network/service information) without triggering user interaction. No public proof-of-concept is identified, and exploitation requires the attacker to already have low-privileged local code execution on the device, limiting it to a post-compromise or malicious-app context.