CVE-2025-54648VulnerabilityPublished 6 Aug 2025

CVE-2025-54648: Huawei HarmonyOS · Out-of-bounds Read

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

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

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: 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: None: There is no loss of integrity within 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 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	Fixed in–

AI-suggested

To mitigate CVE-2025-54648 effectively, European organizations should: 1) Monitor Huawei's official security advisories closely for patches or firmware updates addressing this vulnerability and apply them promptly once available. 2) Restrict NearLink protocol usage to trusted environments and limit wireless exposure by disabling NearLink on devices where it is not essential. 3) Implement network segmentation and wireless access controls to reduce the attack surface, ensuring that only authorized devices can communicate via NearLink. 4) Employ intrusion detection systems capable of monitoring NearLink traffic anomalies or malformed packets indicative of exploitation attempts. 5) Conduct regular security assessments and penetration testing focusing on wireless communication protocols to identify potential exploitation vectors. 6) Educate users and administrators about the risks associated with wireless protocol vulnerabilities and enforce policies to minimize unnecessary wireless connectivity. 7) Consider deploying endpoint protection solutions that can detect abnormal device behavior or crashes potentially caused by exploitation attempts. These steps go beyond generic advice by focusing on protocol-specific controls, environment hardening, and proactive monitoring tailored to the characteristics of the NearLink protocol and HarmonyOS ecosystem.

Description

Out-of-bounds read vulnerability in the SSAP module of the NearLink protocol stack. Impact: Successful exploitation of this vulnerability may affect availability.

Impact

For European organizations, the impact of CVE-2025-54648 depends largely on the adoption of Huawei HarmonyOS devices and the use of NearLink protocol communications within their operational environments. Organizations utilizing HarmonyOS-powered devices, such as smartphones, IoT devices, or embedded systems that rely on NearLink for connectivity, could face service interruptions or device crashes if targeted by an attacker within wireless proximity. This could affect sectors where device availability is critical, including manufacturing, logistics, smart city infrastructure, and telecommunications. Although the confidentiality and integrity impacts are low, availability degradation could disrupt business processes, cause operational delays, or impact user experience. Additionally, in environments with dense device deployments, such as smart factories or connected offices, the vulnerability could be exploited to cause widespread disruptions. The lack of required privileges and user interaction increases the risk, as attackers do not need prior access or user actions to exploit the flaw. However, the adjacent network attack vector limits exploitation to attackers physically or logically close to the target devices, reducing remote attack feasibility. Overall, European organizations using Huawei HarmonyOS devices should consider this vulnerability a moderate risk to operational continuity, especially in wireless communication-dependent scenarios.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

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

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats