CVE-2025-54643VulnerabilityPublished 6 Aug 2025

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

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.6 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.6Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
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: 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: 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 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 =4.0.0 =3.1.0	Fixed in–

AI-suggested

To mitigate CVE-2025-54643, European organizations should implement the following specific measures: 1) Inventory and identify all devices running Huawei HarmonyOS versions 3.1.0 and 4.0.0 within their environment to assess exposure. 2) Apply any available vendor patches or firmware updates promptly once released by Huawei, as no patches were available at the time of disclosure. 3) Restrict local access to devices by enforcing strong physical security controls and limiting user privileges to the minimum necessary, reducing the likelihood of local exploitation. 4) Monitor system logs and kernel events for unusual activity or memory access patterns that could indicate attempts to exploit kernel vulnerabilities. 5) Employ endpoint detection and response (EDR) solutions capable of detecting anomalous kernel-level behavior or privilege escalation attempts on HarmonyOS devices. 6) For critical environments, consider isolating or segmenting HarmonyOS devices to limit lateral movement in case of compromise. 7) Engage with Huawei support channels to obtain timely updates and guidance on vulnerability remediation. 8) Educate IT and security staff about the specific risks of kernel-level vulnerabilities and the importance of maintaining up-to-date device firmware and software. These targeted actions go beyond generic advice by focusing on device-specific inventory, access control, monitoring, and vendor coordination.

Description

Out-of-bounds array access issue due to insufficient data verification in the kernel ambient light module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

Impact

For European organizations, the impact of CVE-2025-54643 centers on potential confidentiality breaches within devices running Huawei HarmonyOS, particularly those using affected versions 3.1.0 and 4.0.0. Since the vulnerability requires local access and low privileges, it poses a risk primarily in environments where devices may be physically accessible or where attackers can gain limited user-level access, such as in corporate mobile device fleets, IoT deployments, or edge computing nodes running HarmonyOS. Confidential data leakage from kernel memory could expose sensitive corporate information, user credentials, or cryptographic keys, undermining data privacy and compliance with regulations like GDPR. The limited integrity and availability impact reduces the risk of system disruption or data manipulation but does not eliminate the threat of espionage or data exfiltration. Given Huawei's market presence in telecommunications and consumer devices in Europe, organizations using HarmonyOS-powered devices in critical infrastructure, telecommunications, or enterprise settings could face targeted attacks exploiting this vulnerability. The absence of known exploits reduces immediate risk but does not preclude future weaponization. Therefore, European entities must assess their exposure, especially in sectors with stringent data protection requirements and where Huawei devices are integrated into operational environments.

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