CVE-2025-27128
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.3 and prior versions allow a local attacker arbitrary code execution in tcb through use after free.
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 confidenceA use-after-free vulnerability in the tcb component of OpenHarmony v5.0.3 and prior versions allows a local attacker to achieve arbitrary code execution by exploiting memory that is accessed after being freed.
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.3CVSS 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 build version or version file in the OpenHarmony installation. Common locations include /etc/version, system/build.prop, or the version field in the system info. Compare the installed version to the affected range <= 5.0.3.Affected if The installed version is 5.0.3 or any prior version (e.g., 5.0.2, 5.0.1, 5.0.0, or earlier releases).
-
Locate tcb componentSearch for the tcb component in the OpenHarmony filesystem. Look for directories or binaries named 'tcb' within the system partition, typically under /system, /vendor, or /data partitions. Check if the tcb directory or binary exists.Affected if The tcb component is present in the OpenHarmony installation.
-
Verify tcb component is enabledInspect the tcb component configuration files or manifest entries. Check for tcb-related configuration in /system/etc, /vendor/etc, or the component manifest. Look for enable flags or service definitions related to tcb.Affected if The tcb component is enabled or configured to run on the system.
-
Check tcb component version or build dateIf a version identifier or build timestamp is available within the tcb component files, retrieve it. This may be found in the binary metadata, a version file within the tcb directory, or build information.Affected if The tcb component version is not newer than the patched version addressing this use-after-free vulnerability.
If OpenHarmony version is 5.0.3 or earlier and the tcb component is present and enabled, the environment is likely affected by this use-after-free vulnerability.
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 a patched version of OpenHarmony beyond v5.0.3; if no patch is available, review and remediate the tcb component's memory management code to eliminate the use-after-free condition.
- 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-27128 — 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-27128 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