VulnerabilityPublished 7 Jul 2025

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

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.9Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% 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:L/I:L/A:L

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Jul 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 2.0.0 – 4.3.0 7 affected builds	Fixed in–

AI-suggested

Given the absence of official patches at this time, European organizations should implement several targeted mitigations: 1) Restrict installation and execution of untrusted third-party call applications on HarmonyOS devices to reduce the attack surface. 2) Employ mobile device management (MDM) solutions to enforce application whitelisting and monitor unusual broadcast activity within the audio framework. 3) Isolate critical Huawei devices on segmented networks to limit local attacker access, as the attack vector is local. 4) Monitor device logs and network traffic for anomalous broadcast messages or audio subsystem errors indicative of exploitation attempts. 5) Engage with Huawei support channels to obtain timely updates or patches and apply them promptly once available. 6) Educate users about the risks of installing unverified call applications and encourage use of official app stores. 7) For organizations deploying HarmonyOS in IoT or embedded systems, consider additional network-level protections such as firewall rules to restrict local broadcast traffic. These measures go beyond generic advice by focusing on controlling application permissions, network segmentation, and proactive monitoring tailored to the vulnerability's characteristics.

Description

Vulnerability that allows third-party call apps to send broadcasts without verification in the audio framework module Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the impact of CVE-2025-53186 depends largely on the deployment of Huawei HarmonyOS devices within their environments. HarmonyOS is primarily used in Huawei smartphones, IoT devices, and smart home products. Organizations relying on Huawei devices for communication or operational technology could face availability disruptions if the vulnerability is exploited, potentially affecting critical audio services such as VoIP calls or voice-controlled systems. Disruptions in audio frameworks could degrade user experience, interrupt communication channels, or cause denial of service in integrated systems. While the confidentiality and integrity impacts are limited, the availability impact could affect business continuity, especially in sectors where real-time communication is vital (e.g., emergency services, customer support centers). Additionally, the lack of required privileges or user interaction for exploitation increases the risk of automated or stealthy attacks within local network environments. European organizations with Huawei device ecosystems should be vigilant, as exploitation could be leveraged as part of broader multi-stage attacks or to cause operational disturbances.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 18:24 UTC

WeaknessesCWE-264

Technical details

References

Community reviews

Related threats