Overview
Whale browser, prior to version 4.32.315.22, has been identified as having a vulnerability that allows attackers to bypass the Same-Origin Policy in a dual-tab environment. This vulnerability, known as CVE-2025-53600, poses a significant risk to users, potentially compromising systems or leading to data leakage.
Vulnerability Summary
CVE ID: CVE-2025-53600
Severity: High (7.5/10 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: Required
Impact: System Compromise or Data Leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Whale Browser | Versions before 4.32.315.22
How the Exploit Works
An attacker can exploit CVE-2025-53600 by manipulating the Same-Origin Policy in a dual-tab environment within the Whale browser. This allows the attacker to access sensitive data, execute scripts or perform actions that would normally be restricted by the browser’s security measures.
Conceptual Example Code
Below is a conceptual example of how the vulnerability might be exploited with a JavaScript injection:
<script>
// Open new tab with target website
var target = window.open('http://target.example.com', '_blank');
// Wait for the target page to fully load
setTimeout(function() {
// Execute malicious actions in the context of the target page
target.document.cookie = "session=malicious_value";
}, 5000);
</script>This code, when run in the context of an attacker’s webpage, would open a new tab to the target site and, after waiting for the page to load, inject a malicious session cookie.
Mitigation Guidance
To mitigate this threat, users should apply the vendor-provided patch as soon as possible. If the patch cannot be applied immediately, temporary mitigation can be achieved through the use of a Web Application Firewall (WAF) or an Intrusion Detection System (IDS).