CVE-2026-54673: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in electron-userland electron-builder
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.
AI Analysis
Technical Summary
The electron-updater component of electron-builder versions before 9.7.0 contains a sensitive information exposure vulnerability (CWE-200). Specifically, the HTTP redirect handler (HttpExecutor.prepareRedirectUrlOptions) only removes the lowercase 'authorization' header during redirects. Other credential headers, including 'PRIVATE-TOKEN' used by GitLab personal access tokens and mixed-case 'Authorization' headers, were not stripped. This flaw could allow these sensitive headers to be sent to attacker-controlled redirect URLs, potentially exposing credentials. The vulnerability is addressed in version 9.7.0.
Potential Impact
Sensitive authentication tokens such as GitLab personal access tokens and OAuth bearer tokens may be exposed to unauthorized actors if an application using a vulnerable version of electron-builder follows an HTTP redirect to a malicious domain. This could lead to credential leakage and unauthorized access to protected resources. The CVSS 4.0 score of 8.2 reflects a high severity due to network attack vector, low attack complexity, and high impact on confidentiality.
Mitigation Recommendations
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.
CVE-2026-54673: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in electron-userland electron-builder
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.
CVSS v4.0
Score 8.2high
Affected software
pkg:github/electron-userland/electron-builderRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The electron-updater component of electron-builder versions before 9.7.0 contains a sensitive information exposure vulnerability (CWE-200). Specifically, the HTTP redirect handler (HttpExecutor.prepareRedirectUrlOptions) only removes the lowercase 'authorization' header during redirects. Other credential headers, including 'PRIVATE-TOKEN' used by GitLab personal access tokens and mixed-case 'Authorization' headers, were not stripped. This flaw could allow these sensitive headers to be sent to attacker-controlled redirect URLs, potentially exposing credentials. The vulnerability is addressed in version 9.7.0.
Potential Impact
Sensitive authentication tokens such as GitLab personal access tokens and OAuth bearer tokens may be exposed to unauthorized actors if an application using a vulnerable version of electron-builder follows an HTTP redirect to a malicious domain. This could lead to credential leakage and unauthorized access to protected resources. The CVSS 4.0 score of 8.2 reflects a high severity due to network attack vector, low attack complexity, and high impact on confidentiality.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-15T22:53:58.560Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4444f227e9c797197e24e1
Added to database: 06/30/2026, 22:36:34 UTC
Last enriched: 07/08/2026, 12:53:32 UTC
Last updated: 08/14/2026, 12:41:11 UTC
Views: 68
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.