VulnerabilityPublished 6 Jun 2025Updated 9 Jun 2025

CVE-2025-48907: Huawei HarmonyOS · Uncaught Exception

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 10:12 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 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: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 Jun 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.0.0	Fixed in–

AI-suggested

To mitigate the risk posed by CVE-2025-48907, European organizations should take the following specific actions: 1) Inventory and identify all Huawei HarmonyOS 5.0.0 devices within their environment to assess exposure. 2) Restrict local access to these devices by enforcing strict physical security controls and limiting network access to trusted users and devices only. 3) Monitor device logs and IPC module behavior for signs of crashes or abnormal exceptions that could indicate exploitation attempts. 4) Engage with Huawei or authorized vendors to obtain and apply patches or firmware updates addressing this vulnerability as soon as they become available. 5) Implement network segmentation to isolate HarmonyOS devices from critical infrastructure to contain potential denial of service impacts. 6) Educate staff about the risks of local attacks and enforce policies to prevent unauthorized device access. 7) Consider deploying endpoint detection and response (EDR) solutions capable of detecting anomalous IPC activity or crashes on HarmonyOS devices. These measures go beyond generic advice by focusing on access control, monitoring, and vendor coordination specific to the affected product and vulnerability characteristics.

Description

Deserialization vulnerability in the IPC module Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the impact of CVE-2025-48907 depends largely on the adoption and deployment of Huawei HarmonyOS devices within their infrastructure. Organizations using HarmonyOS-powered devices, especially in critical environments such as industrial IoT, telecommunications, or smart office ecosystems, may face availability disruptions if an attacker gains local access to these devices and triggers the vulnerability. This could lead to denial of service conditions, potentially interrupting business operations or degrading service quality. While the vulnerability does not compromise data confidentiality or integrity, availability impacts can still cause operational downtime, loss of productivity, and potential cascading effects in interconnected systems. Given the local attack vector, the threat is more relevant in scenarios where physical or local network access is possible, such as within corporate premises or through insider threats. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future exploitation once the vulnerability becomes widely known.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 19:41 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats