dbcve.org
OpenharmonyOperating system · Openatom

CVE-2026-0639

MEDIUM · 5.5 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to after 6.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
in OpenHarmony v6.0 and prior versions allow a local attacker case DOS through missing release of memory.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A memory leak vulnerability in OpenHarmony v6.0 and prior versions allows a local attacker to cause denial of service by exploiting missing memory release. The issue affects availability through resource exhaustion.

MitigationUpgrade to a version newer than v6.0 if available, or obtain and apply vendor-provided patches that address the memory leak. Consider performing a code audit to identify and remediate similar memory management issues.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenharmonyOperating system
Affected:>= 5.0.3, <= 6.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenHarmony installation
    Run command 'cat /etc/os-release' or 'cat /proc/version' to check if OpenHarmony is installed on the system
    Affected if OpenHarmony is present on the system
  2. Determine installed OpenHarmony version
    Run 'hdc shell' then 'getprop ro.build.version.sdk' or check '/system/etc/version' to retrieve the installed version number
    Affected if Unable to determine version or version cannot be retrieved
  3. Compare version against affected range
    Verify the installed version is >= 5.0.3 and <= 6.0 by examining the version output from the previous step
    Affected if Installed version falls within the range 5.0.3 to 6.0 inclusive
  4. Check for memory consumption anomalies
    Monitor system memory usage over time using 'meminfo' or similar tools. Look for steadily increasing memory consumption that is not released
    Affected if System exhibits unexplained memory exhaustion or memory usage continuously grows without recovery

The environment is affected if OpenHarmony is installed with a version between 5.0.3 and 6.0 inclusive, as this is the range where the memory leak vulnerability exists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 6.0
Interim mitigation

Upgrade to a version newer than v6.0 if available, or obtain and apply vendor-provided patches that address the memory leak. Consider performing a code audit to identify and remediate similar memory management issues.

Fix this in Openharmony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0639 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data