Local code execution via undisclosed runtime out-of-bounds write
Published Mar 16, 2026 · Updated Mar 16, 2026
Out-of-bounds write in OpenHarmony 5.0.3 through 5.1.0.x allows local users to execute arbitrary code in pre-installed apps. OpenHarmony identifies arkcompiler_ets_runtime as the affected repository but does not disclose the faulty operation, buffer, or triggering input. Exploitation requires local low-privileged access and a restricted scenario; the vendor's impact assessment records confidentiality loss only.
Summary
What happened
Out-of-bounds write in OpenHarmony 5.0.3 through 5.1.0.x allows local users to execute arbitrary code in pre-installed apps. OpenHarmony identifies arkcompiler_ets_runtime as the affected repository but does not disclose the faulty operation, buffer, or triggering input. Exploitation requires local low-privileged access and a restricted scenario; the vendor's impact assessment records confidentiality loss only.
The record
- CVE
- CVE-2025-41432
- Published
- Mar 16, 2026
- Updated
- Mar 16, 2026
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2026CVE publishedPublication date reported by the CVE source.
- Mar 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v5.0.3 <=v5.1.0.x
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo