CVE-2025-9180
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 · uneditedSame-origin policy bypass in the Graphics: Canvas2D component. This vulnerability was fixed in Firefox 142, Firefox ESR 115.27, Firefox ESR 128.14, Firefox ESR 140.2, Thunderbird 142, Thunderbird 128.14, and Thunderbird 140.2.
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 confidenceA same-origin policy bypass in Firefox and Thunderbird's Canvas2D graphics component allows scripts from one origin to access canvas data from another origin that should be protected. This could enable attackers to exfiltrate sensitive data rendered on canvas elements, such as images from protected sources or data displayed in web applications.
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< 115.27.0< 142.0>= 128.0, < 128.14.0>= 140.0, < 140.2.0< 128.14.0< 142.0>= 140.0, < 140.2.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 Firefox versionRun 'firefox --version' on Linux/macOS, or check Help > About Firefox on Windows/Mac applicationAffected if Version is < 115.27.0, or >= 128.0 and < 128.14.0, or >= 140.0 and < 140.2.0, or >= 142.0 but < 142.0 (any version < 142.0 is affected)
-
Identify installed Thunderbird versionRun 'thunderbird --version' on Linux/macOS, or check Help > About Thunderbird on Windows/Mac applicationAffected if Version is < 128.14.0, or >= 140.0 and < 140.2.0, or >= 142.0 but < 142.0 (any version < 142.0 is affected)
-
Verify Canvas2D component is presentIn Firefox, navigate to about:support and search for 'Canvas' in the Graphics section; the Canvas2D renderer should be listed as activeAffected if Canvas2D is enabled (default state in all affected versions, no toggle exists to disable it)
-
Confirm browser is used for rendering untrusted web contentReview whether Firefox or Thunderbird is used to browse the internet or render HTML email content, which would allow same-origin script access to canvas dataAffected if The browser handles web pages or HTML emails containing potentially malicious scripts that could exploit the Canvas2D same-origin bypass
A user is affected if they run any Firefox version below 142.0 or Thunderbird version below 142.0 (or the specific ESR versions listed), since the Canvas2D component is always enabled and cannot be disabled.
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 · scoped115.27.0128.14.0140.2.0
Update affected installations to Firefox 142 or later, Firefox ESR 115.27/128.14/140.2 or later, or Thunderbird 142/128.14/140.2 or later. For organizations, deploy browser updates via standard patch management.
Firefox 142, Firefox ESR 115.27, Firefox ESR 128.14, Firefox ESR 140.2, Thunderbird 142, Thunderbird 128.14, or Thunderbird 140.2 (depending on current release channel)
- Identify the currently installed Firefox or Thunderbird version via Help > About Firefox/Thunderbird
- For Firefox ESR 115.x users: Upgrade to Firefox ESR 115.27
- For Firefox ESR 128.x users: Upgrade to Firefox ESR 128.14
- For Firefox ESR 140.x users: Upgrade to Firefox ESR 140.2
- For Firefox main release users: Upgrade to Firefox 142
- For Thunderbird users on versions < 128.14.0: Upgrade to Thunderbird 128.14
- For Thunderbird users on versions >= 140.0, < 140.2.0: Upgrade to Thunderbird 140.2
- For Thunderbird users on versions < 142.0: Upgrade to Thunderbird 142
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9180 — 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-2025-9180 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