CVE-2026-6765
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 · uneditedInformation disclosure in the Form Autofill component. This vulnerability was fixed in Firefox 150, Firefox ESR 140.10, Thunderbird 150, and Thunderbird 140.10.
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 · moderate confidenceAn information disclosure vulnerability exists in the Form Autofill component of Firefox, Firefox ESR, and Thunderbird. This flaw allows sensitive information entered into web forms to be potentially exposed. The vulnerability was addressed in Firefox 150, Firefox ESR 140.10, Thunderbird 150, and Thunderbird 140.10.
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< 140.10.0< 150.0< 140.10.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mozilla productCheck if Firefox, Firefox ESR, or Thunderbird is installed. In the application, go to Help > About to see the product name and version. Firefox ESR will say 'Firefox ESR' in the version string.Affected if Product is Firefox, Firefox ESR, or Thunderbird with a version below the fixed releases
-
Check Firefox versionIn Firefox, navigate to about:support or go to Help > About Firefox. Note the version number displayed (e.g., 140.0, 139.0).Affected if Version is below 150.0 (for regular Firefox)
-
Check Firefox ESR versionIn Firefox ESR, navigate to about:support or go to Help > About Firefox. The version will display as 'Firefox ESR 140.x' or similar.Affected if Version is below 140.10.0 (for Firefox ESR)
-
Check Thunderbird versionIn Thunderbird, go to Help > About Thunderbird. Note the version number displayed.Affected if Version is below 140.10.0 (for Thunderbird)
-
Verify Form Autofill is enabledIn Firefox or Thunderbird, go to about:preferences#privacy and scroll to the Form Autofill section. Alternatively, search about:config for 'formfill' or 'autofill' preferences to confirm the feature is active.Affected if Form Autofill is enabled and the version is vulnerable as shown in steps 2-4
A user is affected if they have Firefox below 150.0, Firefox ESR below 140.10.0, or Thunderbird below 140.10.0 with Form Autofill enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped140.10.0150.0
Update affected installations to Firefox 150, Firefox ESR 140.10, Thunderbird 150, Thunderbird 140.10 or later versions. Organizations should inventory all deployed browser installations and ensure consistent patching.
Firefox 150+ / Firefox ESR 140.10+ / Thunderbird 140.10+
- 1. Check the currently installed Firefox version by navigating to about:support in the browser address bar
- 2. Check the currently installed Thunderbird version by navigating to Help > About Thunderbird
- 3. For Firefox users: Download and install Firefox 150.0 or later from www.mozilla.org/firefox/
- 4. For Firefox ESR users: Download and install Firefox ESR 140.10 or later from www.mozilla.org/firefoxfox/esr/
- 5. For Thunderbird users: Download and install Thunderbird 140.10 or later from www.mozilla.org/thunderbird/
- 6. After installation, verify the version by checking about:support (Firefox) or Help > About Thunderbird to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6765 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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