CVE-2023-44402 [Medium] | Security Bypass in Electron

Electron is an open source framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. This only impacts apps that have the `embeddedAsarIntegrityValidation` and `onlyLoadAppFromAsar` fuses enabled. Apps without these fuses enabled are not impacted. This issue is specific to macOS as these fuses are only currently supported on macOS. 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 `.app` bundle on macOS which these fuses are supposed to protect against. There are no app side workarounds, you must update to a patched version of Electron.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-03-04	0.04%	0.11%	+0.08%
2	2026-03-01	0.11%	0.04%	-0.08%
3	2026-02-04	—	0.11%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-03-04

0.04%

0.11%

+0.08%

2026-03-01

0.11%

0.04%

-0.08%

2026-02-04

—

0.11%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.1	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:L) Some sensitive info could get out, but not a total data dump. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:L) Might cause slowdowns, glitches, or partial disruption—not a full brick.	1.3	4.7	[email protected]
7.0	3.1	HIGH	`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.0	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.1

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:H/A:L Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L): Some sensitive info could get out, but not a total data dump.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L): Might cause slowdowns, glitches, or partial disruption—not a full brick.

1.3

4.7

[email protected]

7.0

3.1

HIGH

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.0

5.9

[email protected]

Affected software / configurations for CVE-2023-44402

Vendor	Product	Version	Raw CPE
electronjs	electron	<= 22.3.24	cpe:2.3:a:electronjs:electron::::::node.js::*
electronjs	electron	>= 23.0.0, <= 23.3.14	cpe:2.3:a:electronjs:electron::::::node.js::*
electronjs	electron	>= 24.0.0, <= 24.8.3	cpe:2.3:a:electronjs:electron::::::node.js::*
electronjs	electron	>= 25.0.0, <= 25.8.1	cpe:2.3:a:electronjs:electron::::::node.js::*
electronjs	electron	>= 26.0.0, <= 26.2.1	cpe:2.3:a:electronjs:electron::::::node.js::*
electronjs	electron	27.0.0	cpe:2.3:a:electronjs:electron:27.0.0:alpha1::::node.js::*
electronjs	electron	27.0.0	cpe:2.3:a:electronjs:electron:27.0.0:alpha2::::node.js::*
electronjs	electron	27.0.0	cpe:2.3:a:electronjs:electron:27.0.0:alpha3::::node.js::*
electronjs	electron	27.0.0	cpe:2.3:a:electronjs:electron:27.0.0:alpha4::::node.js::*
electronjs	electron	27.0.0	cpe:2.3:a:electronjs:electron:27.0.0:alpha5::::node.js::*
electronjs	electron	27.0.0	cpe:2.3:a:electronjs:electron:27.0.0:alpha6::::node.js::*

References for CVE-2023-44402

URL	Tags
https://github.com/electron/electron/pull/39788	Issue Tracking
https://github.com/electron/electron/security/advisories/GHSA-7m48-wc93-9g85	Vendor Advisory
https://www.electronjs.org/docs/latest/tutorial/fuses	Product

URL

CVE-2023-44402 | ASAR Integrity bypass via filetype confusion in electron

Exploit prediction scoring system (EPSS) score for CVE-2023-44402

Common vulnerability scoring system (CVSS) metrics for CVE-2023-44402

Weakness enumeration for CVE-2023-44402

GitHub Security Advisory for CVE-2023-44402

Affected software / configurations for CVE-2023-44402

References for CVE-2023-44402