CVE-2023-39281 [Critical] | Memory Corruption in Insydeh2o

CVE-2023-39281 is rated Moderate Risk (52.7/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.49%). Review affected assets and schedule remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.25%	0.49%	+0.23%
2	2026-05-12	0.23%	0.25%	+0.02%
3	2025-11-21	—	0.23%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.25%

0.49%

+0.23%

2026-05-12

0.23%

0.25%

+0.02%

2025-11-21

—

0.23%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. 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:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. 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.	3.9	5.9	[email protected]
5.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N` 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:H) They need powerful rights—admin, root, or similar—before this pays off. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. 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:N) Service keeps running; no real outage angle.	0.5	5.2	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.8

3.1

CRITICAL

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

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
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:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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.

3.9

5.9

[email protected]

5.7

3.1

MEDIUM

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N 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:H): They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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:N): Service keeps running; no real outage angle.

0.5

5.2

134c704f-9b21-4f2e-91b3-4a467353bcc0

Affected software / configurations for CVE-2023-39281

Vendor	Product	Version	Raw CPE
insyde	insydeh2o	05.45.24.0039	cpe:2.3:a:insyde:insydeh2o:05.45.24.0039:::::::*
insyde	insydeh2o	05.44.45.0017	cpe:2.3:a:insyde:insydeh2o:05.44.45.0017:::::::*
insyde	insydeh2o	05.44.34.0055	cpe:2.3:a:insyde:insydeh2o:05.44.34.0055:::::::*
insyde	insydeh2o	05.53.28.0013	cpe:2.3:a:insyde:insydeh2o:05.53.28.0013:::::::*
insyde	insydeh2o	05.45.38.0005	cpe:2.3:a:insyde:insydeh2o:05.45.38.0005:::::::*
insyde	insydeh2o	05.53.23.0011	cpe:2.3:a:insyde:insydeh2o:05.53.23.0011:::::::*
insyde	insydeh2o	05.53.23.0014	cpe:2.3:a:insyde:insydeh2o:05.53.23.0014:::::::*
insyde	insydeh2o	05.53.22.0008	cpe:2.3:a:insyde:insydeh2o:05.53.22.0008:::::::*
insyde	insydeh2o	05.44.30.0022	cpe:2.3:a:insyde:insydeh2o:05.44.30.0022:::::::*
insyde	insydeh2o	05.43.06.0021	cpe:2.3:a:insyde:insydeh2o:05.43.06.0021:::::::*
insyde	insydeh2o	05.42.37.0031	cpe:2.3:a:insyde:insydeh2o:05.42.37.0031:::::::*

References for CVE-2023-39281

URL	Tags
https://www.insyde.com/security-pledge	Vendor Advisory
https://www.insyde.com/security-pledge/SA-2023054	Vendor Advisory

URL

CVE-2023-39281

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

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

Weakness enumeration for CVE-2023-39281

Affected software / configurations for CVE-2023-39281

References for CVE-2023-39281