CVE-2025-54654
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 · uneditedPermission control vulnerability in the Gallery module. Successful exploitation of this vulnerability may affect service confidentiality
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 confidenceThis is a permission control vulnerability in the Gallery module where improper access controls allow unauthorized access to gallery content or functionality, impacting service confidentiality.
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.1= 5.1.0CVSS 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.
-
Verify HarmonyOS versionCheck the device or system settings to confirm the installed HarmonyOS version number (typically found under Settings > About Device > HarmonyOS version)Affected if The installed version is exactly 5.0.1 or exactly 5.1.0
-
Identify Gallery module presenceLocate the Gallery module in the system application list or package manager (on HarmonyOS devices, check Applications or find a 'Gallery' or 'Photos' app entry)Affected if The Gallery module is present and accessible on the device
-
Confirm Gallery module versionIf accessible, check the Gallery/Photos application version through the device app info screen (Settings > Apps > Gallery > Version) or package manager outputAffected if The Gallery module version corresponds to the affected HarmonyOS versions 5.0.1 or 5.1.0
-
Inspect Gallery access control configurationExamine the Gallery module's permission settings and role-based access control (RBAC) configuration files, typically found in system config directories or the app's manifestAffected if Improper or missing RBAC rules are detected that allow unauthorized access to gallery resources
The environment is affected if running HarmonyOS version 5.0.1 or 5.1.0 with the Gallery module enabled and improper access controls are present.
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 · scopedReview and enforce proper role-based access controls (RBAC) in the Gallery module, ensuring users can only access gallery resources they are explicitly authorized to view.
HarmonyOS 5.1.1 or later (latest stable release)
- Check the current HarmonyOS version on the device through Settings > About Phone > Version
- Navigate to Settings > System & Updates > Software Update to check for available updates
- If an update is available, download and install the latest HarmonyOS version (5.1.1 or later)
- After updating, verify the Gallery app has been updated to the latest bundled version
- Restart the device to ensure all permission changes take effect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54654 — 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-54654 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