Skip to main content
CVE-2026-24927VulnerabilityPublished

CVE-2026-24927: Huawei HarmonyOS · Use After Free

Affects Huawei HarmonyOSSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.5Medium
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:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
HuaweiHarmonyOSAffected
  • =4.3.1
  • =4.3.0
  • =4.2.0
  • =4.0.0
Fixed in–
HuaweiEMUIAffected
  • =15.0.0
  • =14.2.0
  • =14.0.0
Fixed in–
Huaweihuawei/harmonyospkg:deb/huawei/harmonyosOther threatsAffected
  • =4.0.0
  • =4.2.0
  • =4.3.0
  • =4.3.1
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. Monitor Huawei's official security advisories for patches addressing CVE-2026-24927 and apply them promptly once released. 2. Restrict local access to HarmonyOS devices by enforcing strict access controls and limiting physical or remote local user privileges. 3. Implement network segmentation to isolate critical HarmonyOS-based systems, reducing the risk of lateral movement if exploitation occurs. 4. Employ endpoint detection and response (EDR) solutions capable of monitoring unusual memory access patterns or crashes indicative of use-after-free exploitation attempts. 5. Conduct regular security audits and penetration tests focusing on local privilege escalation and memory corruption vulnerabilities. 6. Educate users and administrators about the risks of local access vulnerabilities and enforce policies to prevent unauthorized device access. 7. Where feasible, consider alternative platforms or additional security layers for critical systems until patches are available.

Description

Out-of-bounds access vulnerability in the frequency modulation module. Impact: Successful exploitation of this vulnerability may affect availability.

References

Community reviews

Loading reviews…