Skip to main content
VulnerabilityPublished

CVE-2026-54673: electron-builder · Information Exposure

Affects electron-builderSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 26.15.0 soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.15.0, 9.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade electron-builder to 26.15.0; builder-util-runtime and electron-userland/electron-builder to 9.7.0.

Affected software

ProductAffectedFixed in
electron-userlandelectron-builderAffected
  • <26.15.0
Fixed in
  • 26.15.0
electron-userlandbuilder-util-runtimeAffected
  • <9.7.0
Fixed in
  • 9.7.0
GitHubelectron-userland/electron-builderpkg:github/electron-userland/electron-builderOther threatsAffected
  • <9.7.0
Fixed in
  • 9.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade electron-builder to version 9.7.0 or later, where this issue has been fixed. No other mitigations are specified. Patch status is confirmed fixed in 9.7.0.

Description

electron-updater allows for automatic updates for Electron apps. Prior to 9.7.0, the HTTP redirect handler (HttpExecutor.prepareRedirectUrlOptions) only stripped a credential header whose key string matched exactly lowercase "authorization", exposing credentials. Other credential-bearing headers — most notably PRIVATE-TOKEN (used by GitLab's personal access token flow) and mixed-case Authorization (used by GitLab's Bearer/OAuth flow) — were not stripped and could be forwarded to an attacker-controlled cross-origin redirect destination. This issue has been fixed in version 9.7.0.

References

Community reviews

Loading reviews…