CVE-2025-48980: Vulnerability in Brave Desktop Browser
In Brave Browser Desktop versions prior to 1.83.10 that have the split view feature enabled, the "Open Link in Split View" context menu item did not respect the SameSite cookie attribute. Therefore SameSite=Strict cookies would be sent on a cross-site navigation using this method.
AI Analysis
Technical Summary
CVE-2025-48980 is a vulnerability identified in the Brave Desktop Browser versions prior to 1.83.10, specifically affecting the split view feature. The vulnerability arises because the "Open Link in Split View" context menu option does not properly enforce the SameSite cookie attribute, particularly SameSite=Strict. Normally, the SameSite=Strict attribute prevents cookies from being sent on cross-site requests, thereby mitigating cross-site request forgery (CSRF) and cross-site leakage risks. However, in this case, when a user opens a link in split view, the browser incorrectly sends SameSite=Strict cookies along with the cross-site navigation request. This behavior violates the intended security model of the SameSite attribute, potentially allowing malicious sites or actors to gain access to sensitive cookie data that should have been restricted. The vulnerability does not affect cookie integrity or availability but compromises confidentiality by leaking cookies that may contain authentication tokens or session identifiers. Exploitation requires user interaction (opening a link in split view) but no prior authentication or elevated privileges. The vulnerability is tracked under CWE-565 (Reliance on Cookies without Validation and Integrity Checking). Although no exploits are currently known in the wild, the medium CVSS score of 6.5 reflects the moderate risk posed by this issue. The flaw is particularly relevant for users and organizations that rely on Brave Browser's privacy features and handle sensitive or personal data.
Potential Impact
For European organizations, this vulnerability poses a risk to user privacy and data confidentiality, especially for entities handling sensitive personal information such as financial institutions, healthcare providers, and e-commerce platforms. The unintended transmission of SameSite=Strict cookies during cross-site navigation could lead to session hijacking or unauthorized access to user accounts if attackers can trick users into opening malicious links in split view. This undermines the privacy guarantees that Brave Browser aims to provide, potentially exposing organizations to data protection compliance issues under GDPR. While the vulnerability does not affect system integrity or availability, the confidentiality breach could damage user trust and lead to regulatory penalties. Organizations with employees or customers using vulnerable Brave versions may face increased risk of targeted phishing or social engineering attacks leveraging this flaw. The requirement for user interaction limits mass exploitation but does not eliminate targeted attacks. Overall, the impact is moderate but significant for privacy-conscious European organizations.
Mitigation Recommendations
The primary mitigation is to upgrade Brave Desktop Browser to version 1.83.10 or later, where the vulnerability is fixed. Organizations should enforce browser update policies to ensure all users apply this patch promptly. If immediate upgrading is not feasible, disabling the split view feature in Brave Browser settings can prevent exploitation by eliminating the flawed context menu behavior. Additionally, organizations should educate users about the risks of opening untrusted links in split view and encourage cautious browsing habits. Implementing network-level protections such as web filtering to block known malicious URLs can reduce exposure. Monitoring browser telemetry and logs for unusual cross-site navigation patterns may help detect exploitation attempts. Finally, organizations should review cookie handling policies and consider additional security controls like multi-factor authentication to mitigate potential session hijacking resulting from cookie leakage.
Affected Countries
Germany, France, Netherlands, United Kingdom, Sweden
CVE-2025-48980: Vulnerability in Brave Desktop Browser
Description
In Brave Browser Desktop versions prior to 1.83.10 that have the split view feature enabled, the "Open Link in Split View" context menu item did not respect the SameSite cookie attribute. Therefore SameSite=Strict cookies would be sent on a cross-site navigation using this method.
AI-Powered Analysis
Technical Analysis
CVE-2025-48980 is a vulnerability identified in the Brave Desktop Browser versions prior to 1.83.10, specifically affecting the split view feature. The vulnerability arises because the "Open Link in Split View" context menu option does not properly enforce the SameSite cookie attribute, particularly SameSite=Strict. Normally, the SameSite=Strict attribute prevents cookies from being sent on cross-site requests, thereby mitigating cross-site request forgery (CSRF) and cross-site leakage risks. However, in this case, when a user opens a link in split view, the browser incorrectly sends SameSite=Strict cookies along with the cross-site navigation request. This behavior violates the intended security model of the SameSite attribute, potentially allowing malicious sites or actors to gain access to sensitive cookie data that should have been restricted. The vulnerability does not affect cookie integrity or availability but compromises confidentiality by leaking cookies that may contain authentication tokens or session identifiers. Exploitation requires user interaction (opening a link in split view) but no prior authentication or elevated privileges. The vulnerability is tracked under CWE-565 (Reliance on Cookies without Validation and Integrity Checking). Although no exploits are currently known in the wild, the medium CVSS score of 6.5 reflects the moderate risk posed by this issue. The flaw is particularly relevant for users and organizations that rely on Brave Browser's privacy features and handle sensitive or personal data.
Potential Impact
For European organizations, this vulnerability poses a risk to user privacy and data confidentiality, especially for entities handling sensitive personal information such as financial institutions, healthcare providers, and e-commerce platforms. The unintended transmission of SameSite=Strict cookies during cross-site navigation could lead to session hijacking or unauthorized access to user accounts if attackers can trick users into opening malicious links in split view. This undermines the privacy guarantees that Brave Browser aims to provide, potentially exposing organizations to data protection compliance issues under GDPR. While the vulnerability does not affect system integrity or availability, the confidentiality breach could damage user trust and lead to regulatory penalties. Organizations with employees or customers using vulnerable Brave versions may face increased risk of targeted phishing or social engineering attacks leveraging this flaw. The requirement for user interaction limits mass exploitation but does not eliminate targeted attacks. Overall, the impact is moderate but significant for privacy-conscious European organizations.
Mitigation Recommendations
The primary mitigation is to upgrade Brave Desktop Browser to version 1.83.10 or later, where the vulnerability is fixed. Organizations should enforce browser update policies to ensure all users apply this patch promptly. If immediate upgrading is not feasible, disabling the split view feature in Brave Browser settings can prevent exploitation by eliminating the flawed context menu behavior. Additionally, organizations should educate users about the risks of opening untrusted links in split view and encourage cautious browsing habits. Implementing network-level protections such as web filtering to block known malicious URLs can reduce exposure. Monitoring browser telemetry and logs for unusual cross-site navigation patterns may help detect exploitation attempts. Finally, organizations should review cookie handling policies and consider additional security controls like multi-factor authentication to mitigate potential session hijacking resulting from cookie leakage.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- hackerone
- Date Reserved
- 2025-05-29T15:00:04.773Z
- Cvss Version
- 3.0
- State
- PUBLISHED
Threat ID: 6903f7a3aebfcd5474a4474a
Added to database: 10/30/2025, 11:41:23 PM
Last enriched: 12/1/2025, 9:18:49 PM
Last updated: 12/15/2025, 3:50:45 PM
Views: 155
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14387: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in thimpress LearnPress – WordPress LMS Plugin
MediumCVE-2025-13888: Incorrect Privilege Assignment in Red Hat Red Hat OpenShift GitOps 1.18
CriticalCVE-2025-13824: CWE-763: Release of Invalid Pointer or Reference in Rockwell Automation Micro820®, Micro850®, Micro870®
HighCVE-2025-13823: CWE-1395: Dependency on Vulnerable Third-Party Component in Rockwell Automation Micro820®, Micro850®, Micro870®
HighCVE-2025-34412: CWE-693 Protection Mechanism Failure in EQS Group GmbH Convercent Whistleblowing Platform
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.