{"answers":{"affected":"2 open source packages ship an affected version, including app-builder-lib. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-54672 in the wild and no public exploit code.","fix":"Upgrade app-builder-lib to 26.15.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-54672 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-54672 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- app-builder-lib (npm): affected all versions; fixed in 26.15.0\n- app-builder-lib (npm): affected all versions; fixed in 26.15.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54672/ (Markdown: https://insights.sbomify.com/CVE-2026-54672/index.md)","id":"CVE-2026-54672","markdown":"https://insights.sbomify.com/CVE-2026-54672/index.md","name":"CVE-2026-54672","record":{"aliases":["GHSA-7g7r-gx96-252g"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Electron updater library","requires_auth":"low_privilege","summary":"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.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"electron-builder","vendor":"electron"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"electron-updater: Uncontrolled search path elements within `AppImage` built by `app-builder-lib`","id":"CVE-2026-54672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"electron-updater: Cross-origin redirect leaks `PRIVATE-TOKEN` and mixed-case `Authorization` credentials in `builder-util-runtime`","id":"CVE-2026-54673"},"packages":[{"ecosystem":"npm","fixed":["26.15.0"],"introduced":["0"],"last_affected":[],"package":"app-builder-lib","purl":null,"source":"GHSA-7g7r-gx96-252g"},{"ecosystem":"npm","fixed":["26.15.0"],"introduced":["0"],"last_affected":[],"package":"app-builder-lib","purl":"pkg:npm/app-builder-lib","source":"GHSA-7g7r-gx96-252g"}],"prev":{"headline":"WeGIA: Authorization Bypass via Empty Resource Array in InternoControle","id":"CVE-2026-54671"},"products":["app-builder-lib","electron-builder"],"published":"2026-06-30","related":[{"cvss_score":7.5,"headline":"Code Signing Bypass on Windows in electron-updater \u003c 6.3.0-alpha.6","id":"CVE-2024-39698","kev_date_added":null,"published":"2024-07-09"},{"cvss_score":7.3,"headline":"electron-builder's NSIS installer - execute arbitrary code on the target machine (Windows only)","id":"CVE-2024-27303","kev_date_added":null,"published":"2024-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-01","vendors":["electron-userland"]},"summary":"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.","url":"https://insights.sbomify.com/CVE-2026-54672/"}