← Back
CVE-2026-54672
high
CVSS 7.8
Vulnerability in app-builder-lib (CVE-2026-54672)
Summary
vulnerability in app-builder-lib (CVE-2026-54672). Successful exploitation can lead to full system takeover. Exploitable via ``AppImage``. Mitigation: upgrade to `26.15.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54672** has been found in app-builder-lib.
Attackers can target a specific entry point like ``AppImage`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.8/10.
What to do: upgrade app-builder-lib to **26.15.0** or later.
If unsure, ask your IT team or search "app-builder-lib CVE-2026-54672" on the vendor's site.
CVE-2026-54672 (app-builder-lib) — CWE-427 / CVSS v3 7.8
Attack vector: local / no user interaction
Attack surface: `AppImage` / `LD_LIBRARY_PATH` / `AppRun` / `libfoo.so`
Patched: `26.15.0` — apply immediately
Workaround: Set `LD_LIBRARY_PATH` to a non-empty value before launching the `AppImage`, so that the concatenation does not produce an empty path component.
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
**A vulnerability** (CWE-427) exists in app-builder-lib. Attackers reach the vulnerable code path via ``AppImage`` without authentication.
📍 Affected scope
app-builder-lib — . Attack surface: `AppImage` / `LD_LIBRARY_PATH` / `AppRun` / `libfoo.so`.
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **26.15.0**.
🛡️ Workaround
Workaround: Set `LD_LIBRARY_PATH` to a non-empty value before launching the `AppImage`, so that the concatenation does not produce an empty path component.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'app-builder-lib' .` 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 'app-builder-lib' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `app-builder-lib` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Set `LD_LIBRARY_PATH` to a non-empty value before launching the `AppImage`, so that the concatenation does not produce an empty path component.パッチが適用されるまでの応急処置として、Set `LD_LIBRARY_PATH` to a non-empty value before launching the `AppImage`, so that the concatenation does not produce an empty path component. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade app-builder-lib to 26.15.0ステージング環境で 26.15.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
app-builder-lib
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.15.0"}]}]
References
- exploit [email protected]
- patch [email protected]
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54672
- web https://github.com/electron-userland/electron-builder/commit/01b8ba979d1db44543e18d07b4ad94953deb10ea
- web https://github.com/electron-userland/electron-builder/releases/tag/[email protected]
- web https://github.com/advisories/GHSA-7g7r-gx96-252g