dbcve.org
OpenharmonyOperating system · Openatom

CVE-2025-21082

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-08
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 cause apps crash through type confusion.

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

OpenHarmony v5.0.3 and prior versions contain a type confusion vulnerability that allows a local attacker to cause applications to crash. Type confusion occurs when code treats an object of one type as a different type, leading to memory corruption and denial of service.

MitigationApply the vendor patch for CVE-2025-21082 when available; until then, limit device access to trusted users and monitor for application crash reports indicating exploitation attempts.

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 OpenHarmony version
    Use the system version checking mechanism available on the device (such as 'getprop' command, system settings, or /proc/version file) to determine the installed OpenHarmony version
    Affected if The reported version is 5.0.3 or any earlier version (e.g., 5.0.2, 5.0.1, 5.0.0, 4.x, etc.)
  2. Confirm OpenHarmony distribution
    Verify that the target system runs OpenHarmony (Openatom Openharmony) and not another OS fork or derivative
    Affected if The system is confirmed to be running OpenHarmony and the version check shows <= 5.0.3
  3. Review application crash logs
    Examine system logs or crash reports for unexpected application terminations that may indicate exploitation of the type confusion vulnerability
    Affected if Application crashes are observed and the system version is <= 5.0.3, especially if crashes are repetitive or unexplained

A system is affected if it runs OpenHarmony version 5.0.3 or any prior version, as the type confusion vulnerability exists in those releases and can be triggered by a local attacker to cause denial of service.

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 for CVE-2025-21082 when available; until then, limit device access to trusted users and monitor for application crash reports indicating exploitation attempts.

Fix this in Openharmony Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
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,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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