VulnerabilityPublished 11 Oct 2025Updated 14 Oct 2025

CVE-2025-58283: Huawei HarmonyOS · Permissions, Privileges, and Access Controls

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Huawei HarmonyOS	Affected =5.1.0 =5.0.1	Fixed in–

AI-suggested

To mitigate CVE-2025-58283, European organizations should implement the following specific measures: 1) Monitor Huawei’s official channels for patches or firmware updates addressing this vulnerability and apply them promptly once available. 2) Restrict physical and local network access to devices running HarmonyOS, especially in shared or public environments, to reduce the likelihood of attacker proximity. 3) Educate users about the risks of interacting with suspicious prompts or applications that could trigger exploitation, minimizing user interaction risks. 4) Conduct audits of device configurations focusing on Wi-Fi module permissions and access controls to identify and remediate overly permissive settings. 5) Employ endpoint detection and response (EDR) solutions capable of monitoring unusual local activity or privilege escalations related to Wi-Fi services. 6) Segment networks to isolate vulnerable devices and limit lateral movement opportunities. 7) For organizations deploying IoT or telecom infrastructure with HarmonyOS, implement strict device onboarding and access policies to prevent unauthorized local access. These targeted actions go beyond generic advice by focusing on the unique attack vector and affected component.

Description

Permission control vulnerability in the Wi-Fi module. Successful exploitation of this vulnerability may affect service confidentiality.

Impact

For European organizations, the primary impact of CVE-2025-58283 is the potential compromise of confidentiality in wireless communications or services running on Huawei HarmonyOS devices. This could lead to unauthorized disclosure of sensitive data, including corporate or personal information transmitted over Wi-Fi. Although the vulnerability requires local access and user interaction, environments with shared or public access to devices (e.g., offices, public kiosks, or IoT deployments) are at higher risk. The flaw does not affect data integrity or system availability, limiting the scope of damage to information leakage. Organizations relying on Huawei devices for critical communications or infrastructure may face increased risk of espionage or data theft. The absence of known exploits reduces immediate threat but does not eliminate future risk, especially as attackers develop techniques to gain local access or trick users into interaction. The medium severity rating suggests that while the vulnerability is not critical, it warrants timely mitigation to prevent potential confidentiality breaches that could undermine trust and compliance with data protection regulations such as GDPR.

CWE-264Permissions, Privileges, and Access Controls (opens in a new tab)
CategoryOWASP Top 10 A01:2021: Broken Access Control (opens in a new tab)
Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
MITRE does not allow mapping vulnerabilities to this entry; it groups weaknesses rather than naming one.

References

consumer.huawei.com/en/support/bulletin/2025/10/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Oct 2025, 01:04 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats