Skip to content

Firefox and Tor Browser CVE-2026-6770 — IndexedDB Cross-Origin Data Leak Exposes User Browsing Identity

A cross-origin data leakage vulnerability in Firefox and Tor Browser's IndexedDB implementation allows a malicious web page to read data stored by other origins in the IndexedDB API — potentially identifying users by their stored browsing data and breaking the origin isolation that Tor Browser's anonymity model depends on. CVE-2026-6770 is fixed in Firefox 130.0.1 and a Tor Browser update. Tor Browser users should update immediately given the privacy implications.

Article security-architecture

Fingerprint.com security researchers have disclosed CVE-2026-6770, a cross-origin information leakage vulnerability in Firefox and Tor Browser’s implementation of the IndexedDB storage API. The vulnerability bypasses the browser’s cross-origin partitioning of IndexedDB storage, allowing a malicious webpage to enumerate and read IndexedDB data stored by other origins — potentially identifying users by their stored application data and, in Tor Browser, undermining the strict origin isolation that is fundamental to the anonymity model.

How the Vulnerability Works

IndexedDB is a browser-side storage API used by web applications to store structured data client-side — login state indicators, cached application data, user preferences, and application-specific identifiers. Modern browsers implement storage partitioning: IndexedDB databases created in the context of origin-A.com should not be accessible when code is running in the context of origin-B.com.

CVE-2026-6770 is a failure in this partitioning when IndexedDB databases are accessed through a specific combination of shared worker contexts and service worker scope resolution. The flaw causes Firefox to incorrectly identify the storage partition key for database lookups in this context, allowing cross-origin reads of databases that should be isolated.

An attacker can use this to:

  1. Enumerate stored databases: Detect whether a user has a stored IndexedDB database for specific web applications — which reveals which services the user has logged into or actively uses
  2. Read stored data: In applications that store user-identifiable data in IndexedDB (authentication tokens, user IDs, preference values), read that data across the origin boundary
  3. Browser fingerprinting: Use the set of stored databases as a fingerprint — since different users have used different web applications, the IndexedDB database enumeration provides a unique fingerprint value

Tor Browser: Elevated Privacy Risk

For standard Firefox users, the practical risk is cross-site tracking and targeted fingerprinting — significant but within the expected threat model of a general-purpose browser.

For Tor Browser users, the implications are more serious. Tor Browser’s anonymity model depends on strict origin isolation: each browsing tab should be isolated from every other origin, preventing cross-site correlation that could de-anonymise a user. CVE-2026-6770 can allow cross-origin correlation of Tor Browser sessions — if a user’s Tor Browser session has stored any identifiable IndexedDB data (even from a previous session where they were not anonymised), that data can be read by an adversarial page, potentially linking their anonymised Tor session to their real identity.

For journalists, activists, and others relying on Tor Browser for anonymity against sophisticated adversaries, this class of vulnerability has higher practical stakes than for general users.

Affected Versions and Patching

  • Firefox: All versions prior to 130.0.1. Update via Help → About Firefox.
  • Firefox ESR: Versions prior to 128.2.1 ESR.
  • Tor Browser: Tor Browser 14.5.3 and earlier; update to 14.5.4 or later via the Tor Browser update mechanism.

The fix implements correct storage partition key derivation in the shared worker and service worker code paths, ensuring IndexedDB access is correctly scoped to the initiating origin regardless of worker context.

Tor Browser users in high-risk situations (journalists, activists, human rights workers) should treat this as an emergency update and verify Tor Browser is updated before any sensitive browsing session.

Share this article

Related Intelligence

🏛️ Architecture

Microsoft Edge Stores Saved Passwords as Plaintext in Process Memory — No CVE, No Patch

Security researchers have documented that Microsoft Edge's built-in password manager stores user-saved passwords in cleartext within the browser's process memory — readable by any process on the same system with the ability to dump Edge process memory. Microsoft has acknowledged the behaviour and characterised it as a performance design decision, not a vulnerability warranting a security fix. Users relying on Edge's password manager for credential storage should understand what this means for their threat model.

#microsoft-edge +6
🏛️ Architecture

Eclipse BaSyx ICS Platform: CVE-2026-7411 CVSS 10.0 Path Traversal RCE Threatens Industrial Asset Administration

Two critical vulnerabilities in Eclipse BaSyx V2 — the open-source Industrial Internet of Things Asset Administration Shell implementation used in Industry 4.0 infrastructure — allow an unauthenticated attacker to achieve remote code execution and bypass network segmentation. CVE-2026-7411 (CVSS 10.0) enables arbitrary file write on the BaSyx server; CVE-2026-7412 (CVSS 8.6) enables blind SSRF that can bypass OT network isolation. Patches are available in BaSyx V2 milestone-10.

#ics +9
🏛️ Architecture

OpenSSH CVE-2026-35414 — Certificate Authentication Bypass via Comma Bug Grants Root Access

A single-character defect in OpenSSH's certificate Subject Alternative Name parsing allows an attacker with a maliciously crafted certificate to bypass host-based and user certificate authentication entirely, potentially gaining unauthorised access to systems relying on certificate-based SSH for privileged access. Researchers have named the vulnerability SplitSSHell. Operators using OpenSSH certificate authentication for root or privileged user access should review their CA trust chains immediately.

#openssh +6