VulnerabilityPublished 6 Aug 2025

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

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.2Medium

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

EPSS: 0.1% 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:N/S:U/C:N/I:N/A:H

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

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: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 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-54608, European organizations should: 1) Inventory and identify all devices running affected HarmonyOS versions (5.0.1 and 5.1.0) to assess exposure. 2) Restrict physical and local access to Huawei devices to trusted personnel only, minimizing the risk of local exploitation. 3) Monitor for official Huawei security advisories and promptly apply patches or updates once available. 4) Implement application whitelisting and restrict installation of untrusted or unauthorized apps that could exploit local vulnerabilities. 5) Employ endpoint detection and response (EDR) solutions capable of monitoring unusual screen orientation changes or related anomalous behaviors. 6) Educate users about the risks of granting local access and encourage reporting of unexpected device behavior. 7) For IoT deployments, consider network segmentation to isolate vulnerable devices and limit potential impact. These steps go beyond generic advice by focusing on access control, monitoring, and proactive patch management tailored to the specific nature of this vulnerability.

Description

Vulnerability that allows setting screen rotation direction without permission verification in the screen management module. Impact: Successful exploitation of this vulnerability may cause device screen orientation to be arbitrarily set.

Impact

For European organizations, the impact of CVE-2025-54608 is primarily operational disruption on devices running HarmonyOS. Since the vulnerability allows arbitrary screen orientation changes without permission, it could be exploited to degrade user experience or cause confusion, potentially impacting productivity in environments relying on HarmonyOS devices. While it does not compromise data confidentiality or integrity, the availability impact could interfere with critical applications, especially in sectors where device usability is crucial, such as manufacturing, healthcare, or logistics using Huawei devices. The requirement for local access limits remote exploitation risks, but insider threats or physical access scenarios remain relevant. Additionally, organizations using HarmonyOS-based IoT devices might face challenges if screen orientation changes affect device interfaces or monitoring systems. Given Huawei's market presence in Europe is growing but still limited compared to other OS platforms, the overall impact is moderate but should not be overlooked in environments with Huawei device deployments.

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/8/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Aug 2025, 02:49 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats