CVE-2026-27648
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 v6.0 and prior versions allow a remote attacker arbitrary code execution in pre-installed apps.
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 confidenceThis is a remote code execution (RCE) vulnerability in OpenHarmony OS v6.0 and prior versions. The vulnerability allows a remote attacker to execute arbitrary code within the context of pre-installed system applications, potentially granting broad access to device resources and user data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 version via 'getprop ro.build.version.harmonyos' or 'cat /etc/version' or check the About Phone section in system settingsAffected if version is v6.0 or lower (e.g., v5.0, v4.x, v3.x)
-
List pre-installed applicationsExamine /system/app or /preinstall directories, or use 'bm dump -a' command to enumerate all installed packagesAffected if any pre-installed applications exist on the system (this is the attack surface)
-
Check if pre-installed apps are network-exposedUse 'netstat -tulnp' or check /proc/net/tcp to identify listening ports, then correlate with running pre-installed app processes via 'ps -A | grep <app>'Affected if any pre-installed application has a network listener or exposed service running on a port
-
Verify app authentication settingsInspect the app's config.json or manifest file in /data/app/ or /system/app/ for 'allowCommonEvent' or 'permission' configurations, or check if the app exposes unauthenticated IPC/Ability endpointsAffected if pre-installed apps have no authentication requirement for network-accessible interfaces
-
Assess network accessibilityRun 'ip addr show' to get device IP, then test connectivity to any exposed pre-installed app ports from another device on the network using telnet or curlAffected if the device is network-reachable and pre-installed apps expose accessible network services
User is affected if running OpenHarmony v6.0 or prior AND has pre-installed applications that are network-accessible without authentication.
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 available vendor patches for OpenHarmony v6.0 and prior versions. If no patch is available, consider network segmentation to limit exposure to untrusted networks and minimize the attack surface of pre-installed applications.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27648 — 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-2026-27648 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