CVE-2025-20917
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 applying binary of pdf content in Samsung Notes prior to version 4.4.26.71 allows 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 confidenceThis is an out-of-bounds memory read vulnerability in Samsung Notes Android app. When processing PDF content (specifically 'applying binary of pdf content'), the app reads memory beyond allocated buffer boundaries, potentially exposing sensitive heap/stack data to attackers. The vulnerability is triggerable via malicious PDF files opened in the app.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 app versionOpen the Samsung Notes app, tap the menu (three lines), go to Settings, then tap About Samsung Notes to view the version number. Alternatively, check via Settings > Apps > Samsung Notes > App info.Affected if The displayed version number is lower than 4.4.26.71 (for example, 4.4.26.70, 4.4.25.x, or any earlier version).
-
Verify PDF feature usageAttempt to open a PDF file in Samsung Notes by using the Import feature or attaching a PDF to a note. Observe whether the app processes and displays the PDF content.Affected if The app successfully opens and processes PDF files, meaning the vulnerable PDF processing code path is reachable.
-
Confirm Android OS support statusCheck that the device is running a supported Android version where Samsung Notes receives updates. Go to Settings > About Phone > Android version.Affected if Samsung Notes is installed but cannot be updated to version 4.4.26.71 or later due to OS compatibility, leaving the vulnerable version in place.
You are affected if your installed Samsung Notes version is lower than 4.4.26.71 AND you use the app to open or process PDF files.
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. Until updated, avoid opening untrusted PDF files in Samsung Notes.
4.4.26.71
- Open the Samsung Notes app on your Samsung Galaxy device
- Navigate to the app settings or 'About Notes' section to verify the current version number
- Open the Galaxy Store (or Samsung Galaxy Store) app
- Search for 'Samsung Notes' and tap Update to install the latest version
- Alternatively, check for system updates in Settings > Software update to ensure the Notes app is updated through the system update mechanism
- Confirm the installed version is 4.4.26.71 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20917 — 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-20917 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