CVE-2025-20933
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 · uneditedOut-of-bounds read in parsing bmp image in Samsung Notes prior to version 4.4.26.71 allows local attackers to read out-of-bounds memory.
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 confidenceAn out-of-bounds read vulnerability exists in Samsung Notes versions prior to 4.4.26.71 when parsing BMP image files. A local attacker could craft a malicious BMP file that, when opened by the user in Samsung Notes, allows reading beyond allocated buffer boundaries, potentially exposing sensitive memory contents.
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< 4.4.26.71CVSS 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.
-
Check Samsung Notes versionOpen Samsung Notes app, tap the menu (three lines), go to Settings, then About Samsung Notes to view the current version numberAffected if The displayed version is lower than 4.4.26.71 (for example, 4.4.26.70, 4.4.25.x, or earlier)
-
Verify if Samsung Notes can open BMP filesAttempt to open a BMP image file within Samsung Notes, or check the app's supported file types in SettingsAffected if BMP file opening is supported and functional in the installed version
-
Confirm device model compatibilityCheck your Samsung device model number in Settings > About Phone to ensure it runs Samsung NotesAffected if The device supports Samsung Notes and the app version is vulnerable
You are affected if Samsung Notes is installed with a version lower than 4.4.26.71 and the app can parse BMP image files on your device.
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 · scoped4.4.26.71
Update Samsung Notes to version 4.4.26.71 or later. Avoid opening BMP files from untrusted sources.
Samsung Notes version 4.4.26.71
- Open the Galaxy Store app on your Samsung device
- Search for 'Samsung Notes' or navigate to the Apps section
- Locate Samsung Notes in the installed apps list
- Tap on Samsung Notes and select 'Update' if an update is available
- Alternatively, enable auto-updates for Samsung Notes in Galaxy Store settings
- Verify the updated version is 4.4.26.71 or later by checking the app info screen
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20933 — 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-20933 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