CVE-2026-24917: Huawei HarmonyOS · Use After Free
Affects Huawei HarmonyOSSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- 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:H/PR:L/UI:N/S:U/C:H/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Feb 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HuaweiHarmonyOS | Affected
| Fixed in– |
| HuaweiEMUI | Affected
| Fixed in– |
Huaweihuawei/harmonyospkg:deb/huawei/harmonyosOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Restrict local access to HarmonyOS devices by enforcing strict physical security and limiting user privileges to trusted personnel only. 2. Monitor and audit device usage logs to detect unusual local activity that could indicate exploitation attempts. 3. Implement network segmentation to isolate HarmonyOS devices from critical infrastructure to reduce the impact of potential compromise. 4. Apply principle of least privilege on devices and connected systems to minimize the attack surface. 5. Stay informed on Huawei security advisories and apply patches promptly once released. 6. Employ endpoint detection and response (EDR) solutions capable of identifying anomalous behaviors associated with use-after-free exploitation. 7. Conduct regular security training for staff to recognize and report suspicious activity involving local device access. 8. Where possible, consider alternative devices or OS platforms for critical functions until the vulnerability is resolved.
Description
UAF vulnerability in the security module. Impact: Successful exploitation of this vulnerability may affect availability.