Skip to content
Fencer Intel
medium 6.1

CVE-2025-55305 json

Electron is vulnerable to Code Injection via resource modification

published last yr. modified 21d ago also EUVD-2025-26873 , GHSA-vmqv-hx8q-j7mg

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. In versions below 35.7.5, 36.0.0-alpha.1 through 36.8.0, 37.0.0-alpha.1 through 37.3.1 and 38.0.0-alpha.1 through 38.0.0-beta.6, ASAR Integrity Bypass via resource modification. This only impacts apps that have the embeddedAsarIntegrityValidation and onlyLoadAppFromAsar fuses enabled. Apps without these fuses enabled are not impacted. This issue is fixed in versions 35.7.5, 36.8.1, 37.3.1 and 38.0.0-beta.6.

Patch / fix

  • npm electron 35.7.5, 36.8.1, 37.3.1, 38.0.0-beta.6
  • atom electron 35.7.5, 36.8.1, 37.3.1, 38.0.0-beta.6
  • electronjs electron 35.7.5, 36.8.1, 37.3.1, 38.0.0-beta.6

Is CVE-2025-55305 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-55305 updated cvss 6.1

electron: ASAR Integrity Bypass via resource modification

  • Red Hat OpenShift Dev Spaces devspaces/code-rhel9, devspaces-tech-preview/idea-rhel9
    affected: workaround, no fix available “No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L
GitHub 3.1 6.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L

Affected packages

ecosystem package affected fixed in
npm electron
<35.7.5
>=36.0.0-alpha.1, <36.8.1
>=37.0.0-alpha.1, <37.3.1
>=38.0.0-alpha.1, <38.0.0-beta.6
35.7.5
36.8.1
37.3.1
38.0.0-beta.6

Affected products

  • electron electron

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.