InternetApplication · Samsung

CVE-2025-20994

HIGH · 7.1 CVSS v3.1 Published 2025-06-04
Fix available
A fix is available. Upgrade to 28.0.0.59 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper handling of insufficient permission in SyncClientProvider in Samsung Internet installed on non-Samsung Device prior to version 28.0.0.59 allows local attackers to access read and write arbitrary files.

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 confidence

Improper permission handling in SyncClientProvider in Samsung Internet browser (non-Samsung devices, versions prior to 28.0.0.59) allows local attackers to bypass permission checks and perform arbitrary file read/write operations on the device filesystem.

MitigationUpdate Samsung Internet browser to version 28.0.0.59 or later on affected non-Samsung devices to remediate the improper permission handling in SyncClientProvider.

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
InternetApplication
Affected:< 28.0.0.59

CVSS 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
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Samsung Internet browser is installed
    Check for the app package name 'com.sec.android.app.sbrowser' in your device's installed applications via Settings > Apps or using ADB command: 'adb shell pm list packages | grep sbrowser'
    Affected if The package com.sec.android.app.sbrowser is found on the device
  2. Retrieve the installed version of Samsung Internet
    Open Samsung Internet app, go to Settings > About Internet > App version, or use ADB: 'adb shell dumpsys package com.sec.android.app.sbrowser | grep versionName'
    Affected if The displayed version number is lower than 28.0.0.59
  3. Identify the device manufacturer
    Check the device model and manufacturer via Settings > About Phone > Model, or use ADB: 'adb shell getprop ro.product.manufacturer' and 'adb shell getprop ro.product.model'
    Affected if The device is not manufactured by Samsung (e.g., Google, OnePlus, Xiaomi, etc.)
  4. Confirm the vulnerability condition
    Combine the results: verify Samsung Internet version < 28.0.0.59 AND the device is a non-Samsung device
    Affected if Both conditions are true: Samsung Internet version is below 28.0.0.59 AND the device is made by a manufacturer other than Samsung

You are affected if Samsung Internet browser version 28.0.0.59 or earlier is installed on a non-Samsung device, as the improper permission handling in SyncClientProvider only applies under this specific combination.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 28.0.0.59 or later
Fixed in 28.0.0.59
Interim mitigation

Update Samsung Internet browser to version 28.0.0.59 or later on affected non-Samsung devices to remediate the improper permission handling in SyncClientProvider.

Recommended fix High confidence

28.0.0.59

  1. Open the Samsung Internet browser on your device
  2. Navigate to Settings > About Internet to check your current version number
  3. If the version is earlier than 28.0.0.59, open Google Play Store (Android) or Samsung Galaxy Store
  4. Search for Samsung Internet and tap Update to install version 28.0.0.59 or later
  5. Alternatively, enable auto-updates in your app store settings to receive future security updates automatically

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Internet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20994 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20994 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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