CVE-2025-55305 is a medium-severity (CVSS 6.1) Code Injection vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.
Electron is vulnerable to Code Injection via resource modification
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-55305.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
electronnpmDescription
Impact
This only impacts apps that have the embeddedAsarIntegrityValidation and onlyLoadAppFromAsar fuses enabled. Apps without these fuses enabled are not impacted.
Specifically this issue can only be exploited if your app is launched from a filesystem the attacker has write access too. i.e. the ability to edit files inside the resources folder in your app installation on Windows which these fuses are supposed to protect against.
Workarounds
There are no app side workarounds, you must update to a patched version of Electron.
Fixed Versions
38.0.0-beta.637.3.136.8.135.7.5
For more information
If you have any questions or comments about this advisory, email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | electron | all versions | 35.7.5npm install electron@35.7.5 |
| 📦npm | electron | ≥ 36.0.0-alpha.1&&< 36.8.1 | 36.8.1npm install electron@36.8.1 |
| 📦npm | electron | ≥ 37.0.0-alpha.1&&< 37.3.1 | 37.3.1npm install electron@37.3.1 |
| 📦npm | electron | ≥ 38.0.0-alpha.1&&< 38.0.0-beta.6 | 38.0.0-beta.6npm install electron@38.0.0-beta.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update electron to 35.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-55305 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated Moderate as it requires specific conditions for exploitation: the application must have the `embeddedAsarIntegrityValidation` and `onlyLoadAppFromAsar` fuses enabled, and the attacker must already have local write access to the application’s installation directory.
No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.Source: Red Hat security advisory for CVE-2025-55305 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-55305 in your dependencies?
Find it across npm, including transitive dependencies.