dbcve.org
InternetApplication · Samsung

CVE-2025-58485

MEDIUM · 5.5 CVSS v3.1 Published 2025-12-02
Fix available
A fix is available. Upgrade to 29.0.0.48 or later.
See remediation →
57/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 input validation in Samsung Internet prior to version 29.0.0.48 allows local attackers to inject arbitrary script.

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 · moderate confidence

Cross-site scripting (XSS) vulnerability in Samsung Internet browser versions prior to 29.0.0.48 due to improper input validation. Local attackers can inject arbitrary JavaScript through insufficient sanitization of input, potentially allowing session hijacking or theft of sensitive data.

MitigationUpdate Samsung Internet browser to version 29.0.0.48 or later to receive the patch. Organizations should deploy the update via mobile device management (MDM) to ensure all managed devices are patched.

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:< 29.0.0.48

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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. Verify Samsung Internet browser is installed
    On the Android device, navigate to Settings > Apps, or locate the Samsung Internet icon in the app drawer. Confirm the browser application is present on the device.
    Affected if Samsung Internet browser is installed on the device
  2. Retrieve the installed version number
    Open Samsung Internet browser, tap the three-line menu icon, select Settings, then tap About Internet. Alternatively, go to Settings > Apps > Samsung Internet > App info. Note the version number displayed.
    Affected if A version number is displayed (proceeding to next check)
  3. Compare version against affected range
    Review the version number obtained from the About Internet or App info screen. Compare it numerically to the affected threshold of 29.0.0.48.
    Affected if The displayed version is lower than 29.0.0.48 (for example, 29.0.0.46, 28.0.0.100, or any version below 29.0.0.48)
  4. Confirm the XSS attack surface exists
    Understand that this vulnerability allows injection of arbitrary JavaScript through insufficient input sanitization. The flaw is exploitable when the browser processes certain unsanitized input.
    Affected if Samsung Internet version is below 29.0.0.48 and the browser handles user-supplied web content

The device is affected if Samsung Internet browser is installed and the installed version is lower than 29.0.0.48.

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 29.0.0.48 or later
Fixed in 29.0.0.48
Interim mitigation

Update Samsung Internet browser to version 29.0.0.48 or later to receive the patch. Organizations should deploy the update via mobile device management (MDM) to ensure all managed devices are patched.

Recommended fix High confidence

29.0.0.48

  1. Open the Galaxy Store app on your Samsung device
  2. Search for 'Samsung Internet' or locate it in your installed apps
  3. Tap on Samsung Internet and select 'Update' to install version 29.0.0.48 or later
  4. Alternatively, open the Google Play Store, search for Samsung Internet, and tap Update if a newer version is available
  5. Verify the installed version by opening Samsung Internet, going to Settings > About Internet > Version number to confirm it shows 29.0.0.48 or higher

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

Fix this in Internet Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-58485 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