CVE-2025-20950
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 · uneditedUse of implicit intent for sensitive communication in SamsungNotes prior to version 4.4.26.45 allows local attackers to access sensitive information.
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 confidenceThis is an Android intent hijacking vulnerability in Samsung's Notes application. The app uses implicit intents to transmit sensitive data between components, which allows any local malicious app to intercept or intercept these intents due to Android's intent resolution behavior. A local attacker can exploit this to access notes and other sensitive information stored in or processed by SamsungNotes.
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.45CVSS 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 if Samsung Notes is installedRun 'adb shell pm list packages | grep samsung.notes' or use PackageManager to query for package name 'com.samsung.android.app.notes'Affected if The package is not found, meaning Samsung Notes is not installed on the device (not affected)
-
Retrieve the installed version of Samsung NotesRun 'adb shell dumpsys package com.samsung.android.app.notes | grep versionName' or use a device management tool to query the package versionAffected if Unable to retrieve version information (cannot determine if affected)
-
Compare the installed version to the affected rangeParse the version string obtained from step 2 and compare it numerically to 4.4.26.45 using semantic version comparisonAffected if The installed version is less than 4.4.26.45 (e.g., 4.4.26.40, 4.3.15.2, etc.) - the device is vulnerable
The device is affected if Samsung Notes is installed with a version number lower than 4.4.26.45, since the vulnerable implicit intent handling is present in those versions.
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.45
Update SamsungNotes to version 4.4.26.45 or later. Organizations should enforce this update via MDM/EMM solutions for managed devices and verify the update has been applied.
Samsung Notes version 4.4.26.45
- Open Galaxy Store or Google Play Store on the Samsung device
- Search for 'Samsung Notes' or locate it in your installed apps
- Tap 'Update' to install version 4.4.26.45 or later
- Alternatively, go to Settings > Apps > Samsung Notes > Update
- Verify the installed version is 4.4.26.45 or higher after updating
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-20950 — 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-20950 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