Local code execution via TCB race condition
Published Aug 11, 2025 · Updated Aug 11, 2025
Race condition in liteos_a in OpenHarmony 5.0.3 through 5.0.3.x allows local users to execute arbitrary code in the TCB component. OpenHarmony identifies the affected locus only as TCB and does not disclose which shared resource lacks synchronization or which racing operation corrupts state. Low privileges and no user interaction are required; successful exploitation crosses a security boundary, exposes data, and enables service interruption.
Summary
What happened
Race condition in liteos_a in OpenHarmony 5.0.3 through 5.0.3.x allows local users to execute arbitrary code in the TCB component. OpenHarmony identifies the affected locus only as TCB and does not disclose which shared resource lacks synchronization or which racing operation corrupts state. Low privileges and no user interaction are required; successful exploitation crosses a security boundary, exposes data, and enables service interruption.
The record
- CVE
- CVE-2025-27577
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- OpenHarmony
- Product
- OpenHarmony
- Classifications
- CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 2025Record 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.0.3.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.
Weakness, pattern, technique
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