VulnerabilityPublished 14 Jan 2026

CVE-2025-68959: Huawei HarmonyOS · Information Exposure

Affects Huawei HarmonyOSSource CVE Database V5

Not known to be exploited · CVSS 6.2 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

6.2Medium

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:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
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: 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: 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 14 Jan 2026
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
HuaweiHarmonyOS	Affected 3.0.0 – 4.3.1 6 affected builds	Fixed in–
HuaweiEMUI	Affected 13.0.0 – 15.0.0 4 affected builds	Fixed in–

AI-suggested

To mitigate CVE-2025-68959, European organizations should implement strict physical security controls to prevent unauthorized local access to Huawei devices running affected HarmonyOS versions. Device usage policies should restrict access to trusted personnel only and enforce screen locks and encryption to reduce data exposure risk. Monitoring and logging local access attempts can help detect suspicious activity. Organizations should maintain an inventory of devices and their OS versions to identify those at risk. Since no patches are currently available, organizations should engage with Huawei for updates and apply security patches promptly once released. Additionally, consider isolating or limiting the use of vulnerable devices in sensitive environments until remediation is possible. Employ endpoint detection and response (EDR) tools capable of identifying anomalous local access or data exfiltration attempts. User education on the risks of physical device compromise and secure handling of devices is also critical. Finally, evaluate alternative devices or OS platforms if the risk profile is unacceptable and no timely patch is forthcoming.

Description

Permission verification bypass vulnerability in the media library module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

Impact

For European organizations, the primary impact of CVE-2025-68959 is the unauthorized disclosure of sensitive information on devices running affected versions of Huawei HarmonyOS. This could include personal or corporate multimedia data, potentially leading to privacy violations, intellectual property leaks, or exposure of confidential communications. Since exploitation requires local access without privileges or user interaction, the threat is more relevant in scenarios where devices might be physically accessed by unauthorized personnel or compromised insiders. The confidentiality breach could undermine trust in Huawei devices within corporate environments, especially in sectors handling sensitive data such as finance, healthcare, and government. Although the vulnerability does not affect system integrity or availability, the exposure of sensitive data could facilitate further attacks or social engineering campaigns. The lack of known exploits reduces immediate risk but also means organizations must proactively monitor and prepare for potential future attacks. The impact is heightened in environments where Huawei devices are widely deployed and integrated into critical workflows.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 03:05 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats