Categories
CVE-2026-54673 medium CVSS 6.5

Information Disclosure in builder-util-runtime (CVE-2026-54673)

Summary

Vulnerability in builder-util-runtime (CVE-2026-54673). Confidential information can be exposed externally. Exploitable via HttpExecutor.prepareRedirectUrlOptions. Mitigation: upgrade to 9.7.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54673 has been found in builder-util-runtime.
Attackers can target a specific entry point like HttpExecutor.prepareRedirectUrlOptions over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade builder-util-runtime to 9.7.0 or later.
If unsure, ask your IT team or search "builder-util-runtime CVE-2026-54673" on the vendor's site.

CVE-2026-54673 (builder-util-runtime) — CWE-200 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: HttpExecutor.prepareRedirectUrlOptions / Authorization / undefined / direct_asset_url
Patched: 9.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in builder-util-runtime. Attackers reach the vulnerable code path via HttpExecutor.prepareRedirectUrlOptions.

📍 Affected scope

Check the vendor advisory for the affected versions of builder-util-runtime. Attack surface: HttpExecutor.prepareRedirectUrlOptions / Authorization / undefined / direct_asset_url.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 9.7.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'builder-util-runtime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'builder-util-runtime' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で builder-util-runtime を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade builder-util-runtime to 9.7.0

    ステージング環境で 9.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm builder-util-runtime
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"9.7.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details