CVE-2025-49707 [High] | Spoofing in Ecesv6-Series Azure Vm Firmware

CVE-2025-49707 is rated Moderate Risk (52.6/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.38%). Review affected assets and schedule remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-18	0.28%	0.38%	+0.10%
2	2026-05-08	0.06%	0.28%	+0.22%
3	2025-08-16	—	0.06%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-18

0.28%

0.38%

+0.10%

2026-05-08

0.06%

0.28%

+0.22%

2025-08-16

—

0.06%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.9	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. 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:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. 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.	1.5	5.8	[email protected]
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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: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: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:N) Doesn’t really leak secrets in a meaningful 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.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.9

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
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:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
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.

1.5

5.8

[email protected]

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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: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: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:N): Doesn’t really leak secrets in a meaningful 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.

1.8

3.6

[email protected]

Affected software / configurations for CVE-2025-49707

Vendor	Product	Version	Raw CPE
microsoft	ecesv6-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:ecesv6-series_azure_vm_firmware:-:::::::*
microsoft	dcesv6-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:dcesv6-series_azure_vm_firmware:-:::::::*
microsoft	nccadsh100v5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:nccadsh100v5-series_azure_vm_firmware:-:::::::*
microsoft	ecedsv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:ecedsv5-series_azure_vm_firmware:-:::::::*
microsoft	ecesv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:ecesv5-series_azure_vm_firmware:-:::::::*
microsoft	dcedsv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:dcedsv5-series_azure_vm_firmware:-:::::::*
microsoft	dcesv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:dcesv5-series_azure_vm_firmware:-:::::::*
microsoft	ecadsv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:ecadsv5-series_azure_vm_firmware:-:::::::*
microsoft	ecasv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:ecasv5-series_azure_vm_firmware:-:::::::*
microsoft	dcadsv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:dcadsv5-series_azure_vm_firmware:-:::::::*
microsoft	dcasv5-series_azure_vm_firmware	—	cpe:2.3:o:microsoft:dcasv5-series_azure_vm_firmware:-:::::::*

References for CVE-2025-49707

URL	Tags
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-49707	Vendor Advisory

URL

CVE-2025-49707 | Azure Virtual Machines Spoofing Vulnerability

Exploit prediction scoring system (EPSS) score for CVE-2025-49707

Common vulnerability scoring system (CVSS) metrics for CVE-2025-49707

Weakness enumeration for CVE-2025-49707

Affected software / configurations for CVE-2025-49707

References for CVE-2025-49707