CVE-2025-21066
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 the SPI decoder in Samsung Notes prior to version 4.4.30.63 allows local attackers to access 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 the SPI decoder component of Samsung Notes versions prior to 4.4.30.63. The vulnerability allows local attackers to read memory outside the intended buffer boundaries, potentially exposing sensitive data. The SPI decoder likely fails to properly validate bounds when processing input, leading to the memory access violation.
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.30.63CVSS 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
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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 version on deviceOpen Settings > Apps > Samsung Notes, or run `adb shell dumpsys package com.samsung.android.app.notes` to view installed package details and versionInfoAffected if The displayed version is less than 4.4.30.63 or the versionCode is lower than 4430063000
-
Verify exact version stringIn the app info page, locate the version number field; on Samsung devices this typically shows as a two-part version (e.g., 4.4.30.42)Affected if The version string begins with 4.4.30.x where x is less than 63, or shows any version prior to 4.4.30.63
-
Confirm build date if version not clearly displayedCheck device build properties via `adb shell getprop ro.build.date` or the app's last update date in the Play Store / Galaxy StoreAffected if The Notes app was updated before the 4.4.30.63 patch release date
A Samsung Notes installation is affected if its installed version number is below 4.4.30.63, as the out-of-bounds read vulnerability exists in all prior versions of the SPI decoder component.
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.30.63
Update Samsung Notes to version 4.4.30.63 or later to remediate the vulnerability. Organizations managing Samsung devices should verify that the Notes application has been updated across managed endpoints.
4.4.30.63
- Open the Galaxy Store app on your Samsung device
- Search for 'Samsung Notes' or navigate to the Updates section
- Check for available updates for Samsung Notes
- Update to version 4.4.30.63 or later if an update is available
- Alternatively, check Google Play Store for Samsung Notes updates and update to version 4.4.30.63 or later
- Verify the updated version by opening Samsung Notes > accessing Settings > About Notes to confirm version 4.4.30.63 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21066 — 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-21066 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