CVE-2025-54624VulnerabilityPublished 6 Aug 2025

CVE-2025-54624: Huawei HarmonyOS · Permission Issues

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 06:26 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 4% 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-26.

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

1. Immediate mitigation should focus on network segmentation to limit adjacent network access to Huawei HarmonyOS devices, reducing the attack surface. 2. Implement strict access controls and monitoring on devices running HarmonyOS to detect unusual injection events or anomalous input behavior. 3. Apply principle of least privilege rigorously to limit the permissions of users and processes interacting with the multimodalinput module. 4. Engage with Huawei for official patches or updates addressing CVE-2025-54624 and prioritize deployment once available. 5. Conduct thorough inventory and risk assessment of all HarmonyOS devices within the organization to identify exposure. 6. Use endpoint detection and response (EDR) tools capable of monitoring input event anomalies and suspicious network activity around these devices. 7. For critical environments, consider temporary isolation or replacement of vulnerable devices until patches are applied. 8. Train security teams to recognize signs of exploitation related to input injection attacks and prepare incident response plans accordingly.

Description

Unexpected injection event vulnerability in the multimodalinput module. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the impact of CVE-2025-54624 depends on the extent of HarmonyOS device usage within their infrastructure or supply chain. Enterprises using Huawei devices running HarmonyOS 5.0.1 or 5.1.0 in operational technology (OT), IoT deployments, or mobile endpoints could face confidentiality breaches if attackers exploit this vulnerability. The high confidentiality impact means sensitive data processed or stored on these devices could be exposed. Additionally, the potential availability impact could disrupt critical business operations relying on these devices, especially in sectors like manufacturing, telecommunications, or smart city infrastructure where Huawei devices are integrated. The requirement for adjacent network access limits remote exploitation but does not eliminate risk in environments with shared networks or compromised internal segments. The low privilege requirement means that an attacker who has gained limited access to the network or device could escalate their capabilities or move laterally. The absence of known exploits reduces immediate risk but does not preclude future exploitation. European organizations should be aware of this vulnerability particularly if they operate in sectors with Huawei device deployments or have supply chain dependencies involving HarmonyOS devices.

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, 03:06 UTC

WeaknessesCWE-275

Technical details

References

Community reviews

Related threats