FirefoxWeb browser · Mozilla
CVE-2025-11152
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 · uneditedSandbox escape due to integer overflow in the Graphics: Canvas2D component. This vulnerability was fixed in Firefox 143.0.3.
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 confidenceFirefox contains a sandbox escape vulnerability caused by an integer overflow in the Graphics: Canvas2D component. This memory corruption flaw allows a remote attacker to escape the browser's sandbox isolation and execute arbitrary code outside the restricted environment.
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
< 143.0.3CVSS 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
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L
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 browsersCheck common installation paths: Windows (C:\Program Files\Mozilla Firefox\firefox.exe), macOS (/Applications/Firefox.app), Linux (/usr/lib/firefox or /opt/firefox). On Windows, also query registry key HKLM\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersionAffected if Firefox is found on the system
-
Determine the exact Firefox versionRun 'firefox --version' on Linux, check the application bundle version on macOS (defaults read /Applications/Firefox.app/Contents/Info CFBundleShortVersionString), or read the Version value from the registry key on WindowsAffected if A version number is retrieved
-
Compare against affected rangeCompare the installed version number to 143.0.3 using semantic version comparison (e.g., 143.0.2 < 143.0.3, 142.0 < 143.0.3)Affected if Installed version is below 143.0.3 (e.g., 143.0.2, 142.0, 141.0)
-
Check for multiple Firefox installationsSearch for all firefox executables on the system: Windows (dir /s C:\firefox.exe), macOS (mdfind kMDItemFSName == 'firefox'), Linux (find / -name 'firefox' -type f 2>/dev/null)Affected if Multiple Firefox versions exist and any one is below 143.0.3
The environment is affected if any installed Firefox version is lower than 143.0.3.
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 · scoped143.0.3
Update Firefox to version 143.0.3 or later to remediate this vulnerability.
Firefox 143.0.3
- Open Firefox and navigate to Help > About Firefox to check your current version
- Download Firefox 143.0.3 from the official Mozilla website (www.mozilla.org)
- Follow the installation prompts to upgrade to the fixed version
- Restart Firefox after the upgrade completes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11152 — 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-11152 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