Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Exfiltration of hashed SMB credentials on Windows via file:// redirect

CVE-2022-36077GHSA-p2jh-44qj-pf2v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (electron 20.0.1, 19.0.11, 18.3.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm electron

    Affected
    < 18.3.7>= 20.0.0-beta.1, < 20.0.1>= 19.0.0-beta.1, < 19.0.11
    Fixed in
    19.0.11, 20.0.1, 18.3.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
EPSS
  • CVE-2022-36077: 0.62% estimated exploitation activity in the next 30 days; percentile 49.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact When following a redirect, Electron delays a check for redirecting to file:// URLs from other schemes. The contents of the file is not available to the renderer following the redirect, but if the redirect target is a SMB URL such as file://some.website.com/, then in some cases, Windows will connect to that server and attempt NTLM authentication, which can include sending hashed credentials. Patches This issue has been fixed in all current stable versions of Electron. Specifically, these versions contain the fixes: - 21.0.0-beta.1 - 20.0.1 - 19.0.11 - 18.3.7 We recommend all apps upgrade to the latest stable version of Electron. Workarounds If upgrading isn't possible, this issue can be addressed without upgrading by preventing redirects to file:// URLs in the WebContents.on('will-redirect') event, for all WebContents: For more information If you have any questions or comments about this advisory, email us at security@electronjs.org. Credit Thanks to user @coolcoolnoworries for…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-p2jh-44qj-pf2v

  2. Revision 1 · created ·

    Published from osv record GHSA-p2jh-44qj-pf2v

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-36077

Advisory: Exfiltration of hashed SMB credentials on Windows via file:// redirect
IDs: CVE-2022-36077, GHSA-p2jh-44qj-pf2v
Record: https://patchnext.com/advisories/cve-2022-36077 (revision 2, source checked 26 Oct 2026, 12:17 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: electron 20.0.1, 19.0.11, 18.3.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm electron: affected < 18.3.7; >= 20.0.0-beta.1, < 20.0.1; >= 19.0.0-beta.1, < 19.0.11; fixed in 19.0.11, 20.0.1, 18.3.7

## Suggested inspection (read-only)
- `npm ls electron --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on electron.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-p2jh-44qj-pf2v (OSV record GHSA-p2jh-44qj-pf2v lists affected ranges: npm electron >=0 =20.0.0-beta.1 =19.0.0-beta.1 <19.0.11 (fixed))
- Verified: https://github.com/advisories/GHSA-p2jh-44qj-pf2v (GitHub-reviewed advisory GHSA-p2jh-44qj-pf2v lists affected ranges: npm electron >=0 =20.0.0-beta.1 =19.0.0-beta.1 <19.0.11)

Commands are suggestions: review each one before running it.

Loading voting…