dbcve.org
CWE-426Weakness · CWE-426

CVE-2025-11940

HIGH · 7.0 CVSS v3.1 Published 2025-10-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
A security vulnerability has been detected in LibreWolf up to 143.0.4-1 on Windows. This affects an unknown function of the file assets/setup.nsi of the component Installer. Such manipulation leads to uncontrolled search path. The attack must be carried out locally. Attacks of this nature are highly complex. The exploitability is reported as difficult. Upgrading to version 144.0-1 mitigates this issue. The name of the patch is dd10e31dd873e9cb309fad8aed921d45bf905a55. It is suggested to upgrade the affected component.

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

LibreWolf Windows installer (assets/setup.nsi) suffers from an uncontrolled search path vulnerability, allowing local attackers to perform DLL hijacking by placing malicious DLLs in directories searched before the application's expected location. This enables arbitrary code execution with the privileges of the user running the installer.

MitigationUpgrade LibreWolf to version 144.0-1 or later to obtain the patched installer that resolves the uncontrolled search path issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Windows environment
    Verify the operating system is Windows. This vulnerability affects only the LibreWolf Windows installer.
    Affected if Running a non-Windows OS means the installer vulnerability does not apply.
  2. Locate LibreWolf installer
    Search for setup.exe, installer executable, or files in the LibreWolf Windows installation package, particularly the assets/setup.nsi file.
    Affected if No LibreWolf Windows installer present means this specific vulnerability does not apply.
  3. Check installer version
    Determine the version of the LibreWolf installer executable or the installer package. Compare against version 144.0-1.
    Affected if Installer version is earlier than 144.0-1, indicating an unpatched installer that contains the vulnerable assets/setup.nsi.
  4. Identify recent installer execution
    Check system process list or installation history for currently running or recently executed LibreWolf installer processes.
    Affected if The installer (any version) was executed recently, and a lower version than 144.0-1 was used, the DLL hijacking could have occurred.
  5. Audit DLL search path directories
    Examine directories in the system DLL search path that are searched before the installer's intended location (current directory, system directories, PATH).
    Affected if Malicious DLLs found in directories searched before the installer location indicate exploitation has occurred.

A Windows user is affected if they have run or will run a LibreWolf Windows installer version earlier than 144.0-1, as the uncontrolled search path in assets/setup.nsi enables DLL hijacking during installation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade LibreWolf to version 144.0-1 or later to obtain the patched installer that resolves the uncontrolled search path issue.

Recommended fix High confidence

144.0-1

  1. Download LibreWolf version 144.0-1 or later from the official LibreWolf website
  2. Close any running LibreWolf instances
  3. Run the installer for version 144.0-1
  4. Follow the installation prompts to complete the upgrade
  5. Verify the installed version by checking LibreWolf about support page

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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