dbcve.org
WhaleApplication · Navercorp

CVE-2025-53599

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-04
Fix available
A fix is available. Upgrade to 3.9.1.4206 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Whale browser for iOS before 3.9.1.4206 allow an attacker to execute malicious scripts in the browser via a crafted javascript scheme.

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

The Whale browser for iOS before version 3.9.1.4206 contains a vulnerability in its javascript scheme handler that allows arbitrary JavaScript execution through specially crafted javascript: URLs. An attacker can exploit this to run malicious scripts in the context of the browser, potentially stealing session data, manipulating page content, or performing actions on behalf of the user.

MitigationUpdate Whale browser for iOS to version 3.9.1.4206 or later. Organizations should verify all managed devices have applied the update and consider blocking or monitoring javascript: scheme URLs as a defense-in-depth measure.

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
WhaleApplication
Affected:< 3.9.1.4206

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Check if Whale browser for iOS is installed
    Use your MDM (Mobile Device Management) solution or manually check installed apps on iOS devices to determine if the Navercorp Whale browser for iOS is present on any managed devices.
    Affected if Whale browser for iOS is installed on any device in your organization
  2. Determine installed Whale browser for iOS version
    Query your MDM system for the installed application version of Whale browser for iOS, or check the app version directly on the device through Settings > Apps > Whale > Version.
    Affected if Unable to determine the installed version for comparison
  3. Compare version against affected range
    Compare the installed version number to 3.9.1.4206. Any version less than 3.9.1.4206 is affected (for example: 3.9.0.4200, 3.8.5.4100, etc.).
    Affected if Installed version is less than 3.9.1.4206
  4. Verify javascript: scheme handling capability
    This vulnerability is triggered through the javascript: URL scheme handler within the Whale browser. If the browser is in use and untrusted javascript: URLs could be processed, the vulnerability is exploitable.
    Affected if Whale browser versions below 3.9.1.4206 are in active use and can process javascript: URLs

A device is affected if Whale browser for iOS with a version number less than 3.9.1.4206 is installed and in use.

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

Update Whale browser for iOS to version 3.9.1.4206 or later. Organizations should verify all managed devices have applied the update and consider blocking or monitoring javascript: scheme URLs as a defense-in-depth measure.

Recommended fix Moderate confidence

3.9.1.4206

  1. Open the App Store on your iOS device
  2. Search for "Whale" or "Naver Whale" browser
  3. Locate the Whale browser app in the search results
  4. Check the current installed version in the app description
  5. If the installed version is earlier than 3.9.1.4206, tap the Update button to upgrade to the latest version
  6. Alternatively, enable auto-updates in App Store settings to automatically receive security patches
  7. After updating, verify the version number shows 3.9.1.4206 or later

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

Fix this in Whale Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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