← Back
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.
AI summary snake-internal / snake-material-v2
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`` without authentication.
📍 Affected scope
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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'builder-util-runtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `builder-util-runtime` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade builder-util-runtime to 9.7.0ステージング環境で 9.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
builder-util-runtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.7.0"}]}]
References
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- patch [email protected]
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54673
- web https://github.com/electron-userland/electron-builder/pull/9834
- web https://github.com/electron-userland/electron-builder/releases/tag/[email protected]
- web https://github.com/advisories/GHSA-p2f4-r6v6-j797