dbcve.org
FirefoxWeb browser · Mozilla

CVE-2025-3035

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 137.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
By first using the AI chatbot in one tab and later activating it in another tab, the document title of the previous tab would leak into the chat prompt. This vulnerability was fixed in Firefox 137.

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

This is a cross-tab state leakage vulnerability in Firefox's AI chatbot feature. When a user interacts with the AI chatbot in one tab containing a document with a specific title, then activates the chatbot in a different tab, the document title from the previous tab improperly persists and leaks into the chat prompt of the new tab, enabling information disclosure across tab contexts.

MitigationUpgrade to Firefox 137 or later to receive the patch that properly isolates tab state and prevents document title leakage between tabs.

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
FirefoxWeb browser
Affected:< 137.0

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 Firefox version
    Open Firefox, go to Menu > Help > About Firefox, or navigate to about:support, to view the installed version number
    Affected if Version number is less than 137.0 (e.g., 136.x, 136.0.x, 135.x, etc.)
  2. Verify AI chatbot feature presence
    Look for the AI chatbot integration in Firefox. This may appear as an AI assistant icon, prompt bar, or chrome://browser/content/ai-chat feature in the browser chrome. Check about:support for AI-related components or search for 'AI chatbot' in browser settings
    Affected if The AI chatbot feature is present and available in the browser (feature was introduced in Firefox 136)
  3. Confirm cross-tab session state
    Open two different tabs, navigate to different documents with distinct titles, then activate the AI chatbot in each tab sequentially. Observe if the second tab's chatbot prompt retains the document title from the first tab
    Affected if The document title from one tab appears in the chat prompt of another tab when switching between tabs with the AI chatbot active

A user is affected if they run Firefox version below 137.0 AND have the AI chatbot feature enabled, where switching between tabs with different document titles causes the previous tab's title to leak into the new tab's chat prompt.

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

Upgrade to Firefox 137 or later to receive the patch that properly isolates tab state and prevents document title leakage between tabs.

Recommended fix High confidence

Firefox 137.0

  1. Open Firefox and click the menu button (three horizontal lines) in the top-right corner
  2. Select 'Help' from the menu
  3. Click 'About Firefox'
  4. Firefox will automatically check for updates and download the latest version
  5. Click 'Restart to update Firefox' when the update is ready
  6. Verify the version by navigating to the menu > Help > About Firefox and confirm it shows version 137.0 or later

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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