CVE-2025-26691
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 confidenceIn OpenHarmony v5.0.3 and prior, a local attacker can exploit the 'get permission' functionality to obtain sensitive information they should not have access to. This represents a permission boundary bypass where the permission query mechanism improperly discloses information to unauthorized callers.
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 versionCheck the installed OpenHarmony version on the device or system. On OpenHarmony systems, this is typically found in system settings, about device info, or via command line tools like 'hm version' or checking /system/etc/version files if accessible.Affected if The installed version is v5.0.3 or any version prior to it.
-
Check for local application accessDetermine if the system permits locally-installed applications from untrusted sources. Review the application's installation policy or sandbox configuration settings.Affected if The system allows installation or execution of applications from untrusted local sources.
-
Review permission query exposureExamine whether the 'get permission' API or functionality is exposed to local callers without proper authorization checks. This may involve reviewing permission manager configuration or API access controls.Affected if The permission query mechanism can be invoked by unauthorized local applications or processes.
-
Assess user privilege modelVerify the system's user and permission model - check if multiple user profiles or application sandboxing exist and whether local apps can access permission-related system services.Affected if Local applications can interact with permission query services without sufficient isolation from privileged data.
A user is affected if their OpenHarmony installation is version 5.0.3 or earlier AND the system permits untrusted local applications to access the permission query functionality, allowing unauthorized disclosure of sensitive permission information.
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 any available OpenHarmony security updates. Restrict local access to untrusted applications and review permission grants following the principle of least privilege.
- 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-26691 — 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-26691 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