LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21187: Microsoft Power Automate Remote Code Execution Vulnerability

Microsoft Power Automate Remote Code Execution Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-21187 is a high-severity Microsoft Power Automate for Desktop code execution vulnerability. The available data indicates exploitation requires user interaction and local attack conditions, but successful exploitation could compromise confidentiality, integrity, and availability on affected endpoints.

Executive priority

Treat this as a high-priority endpoint patching issue, especially in environments using desktop automation. It is not evidenced as actively exploited in the provided sources, but impact is high if triggered.

Technical view

Microsoft describes this as a Power Automate for Desktop remote code execution issue affecting version 1.0.0.0. CVSS 3.1 is 7.8 with AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. The listed weakness is CWE-94. Microsoft’s advisory is tagged as patch guidance.

Likely exposure

Exposure is most likely on Windows endpoints where Microsoft Power Automate for Desktop version 1.0.0.0 is installed or remains unpatched. The CVSS vector does not describe a network-reachable service exposure.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. CVSS exploit maturity is unproven. Exploitation requires user interaction, no prior privileges, and low attack complexity under local attack conditions.

Researcher notes

Public detail is limited in the supplied bundle. Do not assume exploitability beyond the CVSS vector. Key missing details include root cause, vulnerable component path, fixed build numbers, and Microsoft’s exact remediation mechanics.

Mitigation direction

  • Review Microsoft’s advisory for the official update and deployment guidance.
  • Patch affected Power Automate for Desktop installations promptly.
  • Prioritize managed workstations where Power Automate is installed.
  • Use endpoint management to confirm update coverage.
  • Apply normal least-privilege and application-control controls where feasible.

Validation and detection

  • Inventory endpoints for Power Automate for Desktop installations.
  • Identify systems running version 1.0.0.0 or older affected builds.
  • Confirm Microsoft’s update is installed on affected endpoints.
  • Check vulnerability management tools for CVE-2025-21187 detections.
  • Track exceptions where business systems cannot be patched immediately.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-21187 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-21187Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftPower Automate for Desktop1.0.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.