Skip to main content
CVE-2025-53772VulnerabilityPublished Updated

CVE-2025-53772: Microsoft Web Deploy 4.0 · Deserialization of Untrusted Data

Affects Microsoft Web Deploy 4.0Source CVE Database V5

0

Not known to be exploited · 27% EPSS · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
27.7% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Microsoft Web Deploy 4.0Affected
  • =10.0.2000
Fixed in–

AI-suggested

To mitigate CVE-2025-53772, organizations should implement the following specific measures: 1) Restrict network access to Web Deploy services using firewalls and network segmentation to limit exposure only to trusted administrators and systems. 2) Enforce strict authentication and authorization policies, ensuring that only necessary users have deployment privileges, and regularly audit these permissions. 3) Monitor Web Deploy logs and network traffic for unusual or unauthorized activity indicative of exploitation attempts. 4) Employ application whitelisting and endpoint protection solutions capable of detecting anomalous code execution patterns. 5) Until a vendor patch is released, consider disabling or limiting the use of Web Deploy 4.0 in high-risk environments or replacing it with alternative deployment mechanisms. 6) Maintain up-to-date backups and incident response plans to quickly recover from potential compromises. 7) Stay informed on Microsoft’s advisories for patches or workarounds and apply them promptly once available. These targeted actions go beyond generic advice by focusing on access control, monitoring, and operational adjustments specific to the nature of this deserialization vulnerability.

Description

Deserialization of untrusted data in Web Deploy allows an authorized attacker to execute code over a network.

References

Community reviews

Loading reviews…