CVE-2025-22835
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 · uneditedin OpenHarmony v5.0.2 and prior versions allow a local attacker arbitrary code execution in pre-installed apps through out-of-bounds write. This vulnerability can be exploited only in restricted scenarios.
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 confidenceOpenHarmony v5.0.2 and prior versions contain an out-of-bounds write vulnerability in pre-installed applications that enables a local attacker to achieve arbitrary code execution. The vulnerability is exploitable only in restricted scenarios requiring local access to the device. Despite the limited attack surface, the impact is severe as it allows execution of arbitrary code within pre-installed app contexts.
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>= 4.1.0, <= 5.0.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OpenHarmony versionCheck the system settings or use the command line to retrieve the OpenHarmony version installed on the device (typically found under Settings > About Device > Version or via getprop command)Affected if The installed version is 4.1.0, 4.1.1, 4.1.2, 4.2.0, 4.2.1, 4.2.2, 5.0.0, 5.0.1, or 5.0.2 (any version >= 4.1.0 and <= 5.0.2)
-
Confirm pre-installed applications existList the pre-installed applications on the device - these are apps bundled by the device manufacturer or OS distribution that cannot be uninstalled by normal usersAffected if The device contains any pre-installed applications (this is the default state for most OpenHarmony devices)
-
Verify local access conditionsAssess whether untrusted local users have physical or terminal access to the device, or whether the device runs in multi-user environments where local privilege escalation could occurAffected if The device is accessible to local users beyond the device owner, or runs in shared/untrusted physical locations
You are affected if your OpenHarmony version is between 4.1.0 and 5.0.2 inclusive AND the device has pre-installed applications, which is the standard configuration for OpenHarmony devices.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to OpenHarmony v5.0.2 or later if a patch is available, or work with the vendor for a security update. Since this is a local vulnerability with restricted exploitation scenarios, implement device access controls and minimize local user privileges as a compensating control until a patch is applied.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22835 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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