CVE-2025-20011: in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

Q: How do I fix CVE-2025-20011?

openharmony: upgrade to newer than 5.0.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-20011 being exploited?

CVE-2025-20011 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-20011 affect?

CVE-2025-20011 affects openharmony. Severity is low (CVSS 3.3). in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

Q: How urgent is CVE-2025-20011?

Priority 12/100. No elevated risk signals yet.

Routine

LOW 3.3UPGRADE

CVE-2025-20011 is a low-severity flaw (CVSS 3.3) affecting openharmony. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.3 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-401
Published	2025-03-04
Last modified	2026-06-17

Publisher (CNA): OpenHarmony · Vendor: openatom

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-04 04:15 UTCPublished CVE record published
2026-06-17 08:40 UTCUpdated Record last modified

openatom openharmony UPGRADE

Affected: >= 4.1 and <= 5.0.2

Fixed in: newer than 5.0.2

Safe to downgrade to: a release before 4.1

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-20011?

openharmony: upgrade to newer than 5.0.2. Exact commands for each OS are on this page.

Is CVE-2025-20011 being exploited?

CVE-2025-20011 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-20011 affect?

CVE-2025-20011 affects openharmony. Severity is low (CVSS 3.3). in OpenHarmony v5.0.2 and prior versions allow a local attacker case DOS through missing release of memory.

How urgent is CVE-2025-20011?

Priority 12/100. No elevated risk signals yet.

Related CVEs

CVE-2026-0639 LOW 3.3 UPGRADE in OpenHarmony v6.0 and prior versions allow a local attacker case DOS through missing release of memory.
CVE-2025-6969 MEDIUM 5.0 MITIGATE in OpenHarmony v5.1.0 and prior versions allow a local attacker cause DOS through improper input.
CVE-2025-52458 MEDIUM 5.5 MITIGATE in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps
CVE-2025-41432 MEDIUM 5.5 MITIGATE in OpenHarmony v5.1.0 and prior versions allow a local attacker arbitrary code execution in pre-installed apps
CVE-2025-27577 HIGH 8.4 UPGRADE in OpenHarmony v5.0.3 and prior versions allow a local attacker arbitrary code execution in tcb through race c

References

← Back to latest CVEs