# CVE-2025-62583: Security feature bypass in NAVER Whale browser

> An attacker can escape the iframe sandbox in NAVER Whale browser, bypassing security restrictions in dual-tab environments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** GHSA-5rgq-6cg5-cm5j

## What is CVE-2025-62583?

CVE-2025-62583 is a critical vulnerability in NAVER Whale browser, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Whale Browser before 4.33.325.17 allows an attacker to escape the iframe sandbox in a dual-tab environment.

Weakness: CWE-358 (Improperly Implemented Security Check for Standard)

## Which versions are affected by CVE-2025-62583?

It affects 1 product.


Products: Navercorp Whale.

## How do I fix CVE-2025-62583?

No fix has been published for CVE-2025-62583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62583 being exploited?

There is no known exploitation of CVE-2025-62583 in the wild and no public exploit code.

## Other vulnerabilities in NAVER Whale browser

- [CVE-2025-53599](https://insights.sbomify.com/CVE-2025-53599/): Cross-site scripting in NAVER Whale browser (critical 9.8)
- [CVE-2022-24074](https://insights.sbomify.com/CVE-2022-24074/): Missing authorization in NAVER Whale browser (critical 9.8)
- [CVE-2025-69234](https://insights.sbomify.com/CVE-2025-69234/): Security feature bypass in NAVER Whale browser (critical 9.1)
- [CVE-2018-9859](https://insights.sbomify.com/CVE-2018-9859/): Privilege escalation in n/a (high 8.1)
- [CVE-2018-12449](https://insights.sbomify.com/CVE-2018-12449/): Other in Whale Browser Installer (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62583 and fix it if it is affected.

What it is: CVE-2025-62583 is a critical vulnerability in NAVER Whale browser, published on 16 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62583 in the wild and no public exploit code.

Affected product: NAVER Whale browser. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62583/ (Markdown: https://insights.sbomify.com/CVE-2025-62583/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62583
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62583
- OSV: https://osv.dev/vulnerability/CVE-2025-62583

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62583/
Summaries are generated and may contain mistakes; the official description above is the record.