# CVE-2026-54672: electron-updater: Uncontrolled search path elements within `AppImage` built by `app-builder-lib`

> An attacker can execute arbitrary code by placing a malicious shared library in the launch directory due to unsafe LD_LIBRARY_PATH handling in Electron AppImages.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-7g7r-gx96-252g

## What is CVE-2026-54672?

CVE-2026-54672 is a high-severity code injection vulnerability in electron-userland app-builder-lib, published on 30 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

electron-updater allows for automatic updates for Electron apps. Prior to 26.15.0, AppImage targets built by app-builder-lib could use an empty path component when setting the LD_LIBRARY_PATH environment variable at runtime. This causes the current working directory to be added to the dynamic linker search path, which may allow an attacker to execute arbitrary code by placing a malicious shared library in the directory from which the AppImage is launched. This issue has been fixed in version 26.15.0.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2026-54672?

2 open source packages ship an affected version, including app-builder-lib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `app-builder-lib` | npm | All versions | 26.15.0 |
| `app-builder-lib` | npm | All versions | 26.15.0 |

Products: Electron Electron-Builder.

## How do I fix CVE-2026-54672?

Upgrade app-builder-lib to 26.15.0 or later.

## Is CVE-2026-54672 being exploited?

There is no known exploitation of CVE-2026-54672 in the wild and no public exploit code.

## Other vulnerabilities in electron-userland app-builder-lib

- [CVE-2024-39698](https://insights.sbomify.com/CVE-2024-39698/): Code Signing Bypass on Windows in electron-updater < 6.3.0-alpha.6 (high 7.5)
- [CVE-2024-27303](https://insights.sbomify.com/CVE-2024-27303/): electron-builder's NSIS installer - execute arbitrary code on the target machine (Windows only) (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54672 and fix it if it is affected.

What it is: CVE-2026-54672 is a high-severity code injection vulnerability in electron-userland app-builder-lib, published on 30 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54672 in the wild and no public exploit code.

Affected packages and fixed versions:
- app-builder-lib (npm): affected all versions; fixed in 26.15.0
- app-builder-lib (npm): affected all versions; fixed in 26.15.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54672/ (Markdown: https://insights.sbomify.com/CVE-2026-54672/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54672
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54672
- OSV: https://osv.dev/vulnerability/CVE-2026-54672

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54672/
Summaries are generated and may contain mistakes; the official description above is the record.