CVE-2025-26693
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 cause information leak through get permission.
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.0.3 and prior versions contain a local information disclosure vulnerability in the permission system where the 'get permission' function improperly exposes sensitive information to a local attacker. This allows a local attacker with basic device access to obtain information they should not have permission to view through the permission API.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 versionRun 'getprop ro.build.version.sdk' or check system settings under 'About Device' > 'Version' to find the installed OpenHarmony version numberAffected if The version is 5.0.3 or any earlier version (e.g., 5.0.2, 5.0.1, 4.x releases)
-
Check if permission API is accessibleReview application or system configurations that invoke the 'get permission' API function. Look for code or configuration files that query permission statesAffected if The device or application uses the permission API to retrieve permission details, especially sensitive permission states
-
Verify local access configurationCheck device settings under Settings > Security or Access permissions to determine what local access is granted to basic users or guest accountsAffected if Basic local users or unauthenticated local attackers can access the device and invoke permission queries
-
Audit permission grant statesUse the permission management interface or run 'bm dump -a' (bundle manager) to list all granted permissions on the deviceAffected if Sensitive permissions (such as contacts, location, or messages) are exposed through the vulnerable API to unauthorized local users
A user is affected if their OpenHarmony version is 5.0.3 or prior AND the device allows local access that can invoke the permission API to query sensitive permission states.
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.
dbcve · scopedUpgrade OpenHarmony to a version beyond v5.0.3 that contains the patch for this vulnerability. If no upgrade is available, review and restrict local access permissions as a temporary mitigation.
OpenHarmony version newer than 5.0.3 (e.g., 5.0.4 or latest stable release)
- 1. Check current OpenHarmony version using 'hm version' or checking system settings
- 2. Upgrade OpenHarmony to the latest available release beyond version 5.0.3
- 3. Verify the upgrade completed successfully
- 4. Test that the permission system functions correctly and the information leak vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26693 — 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-26693 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