CVE-2025-54618VulnerabilityPublished 6 Aug 2025

CVE-2025-54618: Huawei HarmonyOS · Permission Issues

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.7 Medium.

Data as of 25 Oct 2026, 18:53 UTC

CVSS 3.1 base score

5.7Medium

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

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

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

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

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: 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 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 2026-10-25.

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 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 this vulnerability, European organizations should implement the following specific measures: 1) Immediately audit and restrict the use of Huawei HarmonyOS devices within sensitive environments, limiting their deployment to non-critical roles until patches are available. 2) Enforce strict access controls and privilege management to ensure that only trusted users have low-level privileges on affected devices, minimizing the attack surface. 3) Monitor clipboard usage and data flows within the network using endpoint detection and response (EDR) tools capable of identifying unusual clipboard access patterns or data exfiltration attempts. 4) Educate users on the risks of sharing sensitive information via clipboard functions, encouraging the use of secure data transfer methods. 5) Maintain close communication with Huawei for timely patch releases and apply updates promptly once available. 6) Consider network segmentation to isolate devices running HarmonyOS from critical systems to reduce lateral movement opportunities. 7) Implement data loss prevention (DLP) solutions that can detect and block unauthorized clipboard data transfers across devices.

Description

Permission control vulnerability in the distributed clipboard module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

Impact

For European organizations, the impact of this vulnerability could be significant, especially for enterprises and government agencies that utilize Huawei HarmonyOS devices within their operational environments. The unauthorized access to clipboard data can lead to leakage of sensitive information, potentially exposing confidential communications, credentials, or intellectual property. This risk is heightened in sectors where data confidentiality is paramount, such as finance, healthcare, and critical infrastructure. Given that the vulnerability requires low-level privileges but no user interaction, insider threats or compromised accounts with limited access could exploit this flaw to escalate data exposure. Additionally, organizations relying on distributed device ecosystems for productivity may face increased risk of data leakage across interconnected devices. Although the vulnerability does not affect system integrity or availability, the confidentiality breach alone could result in regulatory non-compliance under GDPR and damage to organizational reputation.

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:48 UTC

WeaknessesCWE-275

Technical details

References

Community reviews

Related threats