CVE-2025-41432
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.1.0 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.1.0 and prior versions contain an out-of-bounds write vulnerability in pre-installed applications that can be exploited by a local attacker to achieve arbitrary code execution. The vulnerability is classified as high severity (CVSS 7.8) but exploitation is limited to restricted scenarios, likely requiring specific conditions or privileged access within the affected system.
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= 5.0.3= 5.1.0CVSS 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 versionRetrieve the installed OpenHarmony version from the system settings or by querying the system information interface (typically found under Settings > About Device or via system diagnostic commands)Affected if The installed version matches 5.0.3 or 5.1.0 exactly, or is any version prior to 5.1.0 (including 5.0.3)
-
Locate pre-installed applicationsExamine the list of applications that came bundled with the system, typically found in the /system/preinstall/ or /preinstall/ directory on the device filesystem, or via package manager queries that list system-bundled appsAffected if Pre-installed applications exist on the device (these are the attack vector for this CVE)
-
Verify local access conditionsDetermine whether local unprivileged users or third-party applications have the ability to interact with or invoke functionality within pre-installed applications, or if device has developer modes or USB debugging enabled that could allow local code executionAffected if Local attackers can execute code or interact with pre-installed app components (the CVE requires a local attacker scenario)
-
Assess application sandbox statusCheck if the sandboxing or permission model for pre-installed applications restricts their interaction with other apps or system resourcesAffected if Pre-installed applications have elevated privileges or weak sandboxing that could allow an attacker to trigger the out-of-bounds write condition
The environment is affected if running OpenHarmony version 5.0.3 or 5.1.0 (or any prior version) and contains pre-installed applications that can be reached by a local attacker with limited access.
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 dataApply vendor patches from OpenHarmony when available; until then, limit local access to devices running affected versions and restrict installation of untrusted applications to reduce the attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41432 — 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-41432 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