CVE-2025-27563
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 · low confidenceOpenHarmony v5.0.3 and prior versions contain a permission handling flaw that allows a local attacker to bypass intended access controls when querying permission states, resulting in unauthorized information disclosure.
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 system settings or run 'getprop ro.build.version.harmonyos' or 'hiupdmanager --version' to retrieve the installed OpenHarmony versionAffected if Version is 5.0.3 or lower (any version <= 5.0.3)
-
Verify permission query APIs are exposedInspect the application's permission manager module or API endpoint configuration to determine if the permission state query interface is accessible to local applicationsAffected if Permission query APIs are exposed without proper authorization checks
-
Check for the permission bypass conditionReview audit logs or security event logs for unexpected permission state queries from untrusted processes or applicationsAffected if Untrusted local processes can successfully query permission states that should require elevated privileges
-
Confirm vulnerability in permission managerExamine the permission manager service configuration (typically found in /system/etc/ or through the security subsystem) for the specific flaw where query requests bypass the intended authorization checkAffected if The permission manager allows query operations without enforcing proper access control validation
A user is affected if their OpenHarmony installation is version 5.0.3 or prior AND the permission query functionality is accessible to local attackers, allowing unauthorized access to permission state 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.
dbcve · scopedApply available OpenHarmony security patches or update to a version beyond v5.0.3 that addresses the permission check vulnerability.
OpenHarmony version > 5.0.3 (e.g., 5.0.4 or later stable release)
- Upgrade OpenHarmony to a version newer than 5.0.3 to remediate the permission-related information leak vulnerability
- Verify the upgrade does not introduce regressions in permission-related functionality
Generated from the published advisory — verify against the referenced sources before acting.
- 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-27563 — 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-27563 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