dbcve.org
OpenharmonyOperating system · Openatom

CVE-2025-26690

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-11
Fix available
A fix is available. Upgrade to after 5.0.3 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 v5.0.3 and prior versions allow a local attacker case DOS through NULL pointer dereference.

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

In OpenHarmony v5.0.3 and prior versions, a local attacker can cause a Denial of Service condition by triggering a NULL pointer dereference vulnerability. This occurs when the code attempts to access memory through a pointer that has not been initialized or has been explicitly set to NULL, resulting in a system crash or hang.

MitigationApply the vendor patch when available. In the interim, implement proper null-pointer validation checks before dereferencing pointers in the affected code paths to prevent the crash condition.

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

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 the OpenHarmony version
    Run the command 'openharmony-version' or check system build information to determine the exact installed version
    Affected if The installed version is 5.0.3 or any version prior to 5.0.3
  2. Confirm the product is OpenAtom OpenHarmony
    Verify the operating system or embedded platform is Openatom OpenHarmony rather than another distribution
    Affected if The system runs OpenHarmony and the version meets the affected range
  3. Monitor for NULL pointer dereference crashes
    Review system crash logs, kernel logs, or process failure reports for NULL pointer dereference errors in OpenHarmony processes
    Affected if The system experiences unexplained crashes or hangs consistent with NULL pointer dereference and runs a vulnerable version

The environment is affected if it runs OpenAtom OpenHarmony version 5.0.3 or any prior version, as the NULL pointer dereference vulnerability exists in those releases

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 5.0.3
Interim mitigation

Apply the vendor patch when available. In the interim, implement proper null-pointer validation checks before dereferencing pointers in the affected code paths to prevent the crash condition.

Fix this in Openharmony Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-26690 — 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-2025-26690 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