CVE-2025-20967
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 · uneditedImproper access control in Samsung Gallery prior to version 14.5.10.3 in Global Android 13, 14.5.09.3 in China Android 13, and 15.5.04.5 in Android 14 allows attackers to read and write arbitrary file with the privilege of Samsung Gallery.
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 · high confidenceImproper access control in Samsung Gallery allows attackers to read and write arbitrary files with the privilege of the Samsung Gallery application. This critical vulnerability (CVSS 9.1) enables potential unauthorized access to sensitive user media files and other data on the device by bypassing normal file access restrictions.
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< 14.5.10.3< 14.5.09.3< 15.5.04.5CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Locate Samsung Gallery appOpen device Settings, navigate to Apps, and find Samsung Gallery in the application listAffected if Samsung Gallery is installed on the device
-
Check installed versionTap on Samsung Gallery in the apps list, then view the Version or App version field displayed under the app nameAffected if The version displayed is lower than 14.5.10.3 for Global Android 13, lower than 14.5.09.3 for China Android 13, or lower than 15.5.04.5 for Android 14
-
Determine Android versionOpen Settings, go to About Phone, and check the Android version fieldAffected if The device runs Android 13 (Global), Android 13 (China), or Android 14
The device is affected if Samsung Gallery is installed and its version falls below the threshold for the Android version the device runs: 14.5.10.3 for Global Android 13, 14.5.09.3 for China Android 13, or 15.5.04.5 for Android 14.
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 · scoped14.5.09.314.5.10.315.5.04.5
Update Samsung Gallery to version 14.5.10.3 or later for Global Android 13, 14.5.09.3 for China Android 13, or 15.5.04.5 for Android 14. Organizations should deploy these updates via mobile device management (MDM) to ensure fleet-wide remediation.
Gallery 14.5.10.3 (Global Android 13), 14.5.09.3 (China Android 13), 15.5.04.5 (Android 14)
- Open the Galaxy Store or device Settings > Apps > Gallery
- Check for updates and install the latest version
- For Android 13 devices: Update to version 14.5.10.3 or later (Global), or 14.5.09.3 or later (China)
- For Android 14 devices: Update to version 15.5.04.5 or later
- Verify the update was successful by checking Gallery app version in Settings > Apps > Gallery > App info
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20967 — 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-20967 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