CVE-2024-0057 [Critical] | Input Validation Bypass in Powershell

CVE-2024-0057 is rated High Risk (66.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 3.64%). High exploitation likelihood—assess exposure and prioritize remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-02-08	3.73%	3.64%	-0.10%
2	2026-01-27	2.41%	3.73%	+1.32%
3	2026-01-26	—	2.41%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-02-08

3.73%

3.64%

-0.10%

2026-01-27

2.41%

3.73%

+1.32%

2026-01-26

—

2.41%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.1	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N` 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:N) Service keeps running; no real outage angle.	3.9	5.2	[email protected]
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]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.1

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N 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:N): Service keeps running; no real outage angle.

3.9

5.2

[email protected]

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]

OS Trackers for CVE-2024-0057

vendor	priority	summary	link
`alpine`	—	CVE-2024-0057: 5 source package rows (dotnet6-build, dotnet6-runtime, dotnet7-build, dotnet7-runtime, powershell); 13 state rows across 4 repos (3.19-community, 3.20-community, 3.22-community, edge-community); fixed 12, open 1.	https://security.alpinelinux.org/vuln/CVE-2024-0057
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2024-0057
`ubuntu`	medium	CVE-2024-0057 medium priority: Ubuntu including 3 source packages (dotnet6, dotnet7, dotnet8), 24 status rows across 8 suites (bionic, focal, jammy, lunar, mantic, trusty, upstream, xenial): DNE 13, released 10, not-affected 1.	https://ubuntu.com/security/CVE-2024-0057

Affected software / configurations for CVE-2024-0057

Vendor	Product	Version	Raw CPE
microsoft	powershell	>= 7.2, < 7.2.18	cpe:2.3:a:microsoft:powershell::::::::
microsoft	powershell	>= 7.3, < 7.3.11	cpe:2.3:a:microsoft:powershell::::::::
microsoft	powershell	7.4	cpe:2.3:a:microsoft:powershell:7.4:-::::::
microsoft	visual_studio_2022	>= 17.2, < 17.2.23	cpe:2.3:a:microsoft:visual_studio_2022::::::::
microsoft	visual_studio_2022	>= 17.4, < 17.4.15	cpe:2.3:a:microsoft:visual_studio_2022::::::::
microsoft	visual_studio_2022	>= 17.6, < 17.6.11	cpe:2.3:a:microsoft:visual_studio_2022::::::::
microsoft	visual_studio_2022	>= 17.8, < 17.8.4	cpe:2.3:a:microsoft:visual_studio_2022::::::::
microsoft	.net_framework	>= 4.8, < 4.8.04690.02	cpe:2.3:a:microsoft:.net_framework::::::::
microsoft	.net_framework	>= 4.8, < 4.8.04690.01	cpe:2.3:a:microsoft:.net_framework::::::::
microsoft	.net_framework	4.6.2	cpe:2.3:a:microsoft:.net_framework:4.6.2:::::::*
microsoft	.net_framework	4.7	cpe:2.3:a:microsoft:.net_framework:4.7:::::::*
microsoft	.net_framework	4.7.1	cpe:2.3:a:microsoft:.net_framework:4.7.1:::::::*
microsoft	.net_framework	4.7.2	cpe:2.3:a:microsoft:.net_framework:4.7.2:::::::*
microsoft	.net_framework	3.5	cpe:2.3:a:microsoft:.net_framework:3.5:::::::*
microsoft	.net_framework	4.8.1	cpe:2.3:a:microsoft:.net_framework:4.8.1:::::::*
microsoft	.net_framework	2.0	cpe:2.3:a:microsoft:.net_framework:2.0:sp2::::::
microsoft	.net_framework	3.0	cpe:2.3:a:microsoft:.net_framework:3.0:sp2::::::
microsoft	.net	>= 6.0.0, < 6.0.26	cpe:2.3:a:microsoft:.net::::::::
microsoft	.net	>= 7.0.0, < 7.0.15	cpe:2.3:a:microsoft:.net::::::::
microsoft	.net	8.0.0	cpe:2.3:a:microsoft:.net:8.0.0:-::::::

References for CVE-2024-0057

URL	Tags
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-0057	Patch Vendor Advisory
https://security.netapp.com/advisory/ntap-20240208-0007/

URL

CVE-2024-0057 | NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability

Exploit prediction scoring system (EPSS) score for CVE-2024-0057

Common vulnerability scoring system (CVSS) metrics for CVE-2024-0057

Weakness enumeration for CVE-2024-0057

GitHub Security Advisory for CVE-2024-0057

OS Trackers for CVE-2024-0057

Affected software / configurations for CVE-2024-0057

References for CVE-2024-0057