openmcp-client OAuth URL command injection (CVE-2025-58062)
On Windows, openmcp-client mishandled the MCP OAuth authorization URL, allowing PowerShell command injection. This is the same flaw class as mcp-remote and opencode.
What happened
Same open() PowerShell sink class as mcp-remote/opencode: MCP OAuth authorization URL handled unsafely on Windows leading to command injection. Documented in Pillar's comparative analysis of the vulnerability class.
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Unknown steps remain explicit; an edge describes the reported relationship between steps.
- 01 · Full delivery chain is undisclosed
The seed does not specify every connection prerequisite.
Source for step 1 - 02 · Client handles an MCP OAuth URL
The authorization URL is passed to the browser-opening helper.
Hunt: Untrusted content or a changed tool definition precedes a file read, command, or remote call outside the user's intended task.
Process logs cannot recover model intent. Remote connectors and in-process interpreters may produce no local child process. Prompt content alone is not a reliable signature.
Source for step 2 - 03 · Windows shell interprets the URL
Unsafe open() handling exposes a PowerShell command-injection sink.
Hunt: A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
MagicSword policy opportunity · The reported Windows shell branch; an allowed PowerShell interpreter can still run malicious arguments.
Source for step 3 - 04 · Commands execute on the client
The report groups openmcp-client with the same OAuth URL execution class.
Hunt: A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
Source for step 4
Why it matters
Reported impact: The report groups openmcp-client with the same OAuth URL execution class.
Check these source-linked conditions against your setup.
openmcp-client is the affected MCP client in the source account.
Conditions to check- Confirm that the installed version is affected by the historical report; selecting a product does not establish its version or patch status.
- The reported command-injection path depends on Windows OAuth URL handling and an untrusted remote MCP server.
Source-linked applicability guidance. Confirm current scope in the original report.
What you can do
Protection & prevention
Check the vendor advisory and update the affected client; review remote MCP OAuth destinations.
Upgrade clients; never shell-interpolate remote OAuth URLs
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Detection queries
Draft query starters grouped by the attack stages where they apply.
Start with the logs you collect. Each hunt identifies its required visibility, field mapping and limits. Queries are catalog-authored drafts using reusable behavior profiles; test with known activity and your normal baseline before alerting.
02Client handles an MCP OAuth URLUnexpected agent tool useCustom schema · Draft
The authorization URL is passed to the browser-opening helper.
What to look for
Untrusted content or a changed tool definition precedes a file read, command, or remote call outside the user's intended task.
Visibility: Defender-side logs where collected
Required logs
- Agent tool-call audit records with session / tool / destination
- Tool-definition and approval changes
- Endpoint process, file-access and network evidence where available
Coverage limit. Process logs cannot recover model intent. Remote connectors and in-process interpreters may produce no local child process. Prompt content alone is not a reliable signature.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Unexpected agent tool use
id: c709e384-0e11-479e-ab4d-3a06e2431e4b
status: experimental
description: Untrusted content or a changed tool definition precedes a file
read, command, or remote call outside the user's intended task.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- agent.tool.call
- agent.tool.definition.change
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("agent.tool.call", "agent.tool.definition.change")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("agent.tool.call", "agent.tool.definition.change")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Join input provenance, tool descriptions and calls by session ID and compare the action to the approved task.
- Inspect child processes and destinations; record whether execution was in-process, local, or through a remote SaaS connector.
03Windows shell interprets the URLSuspicious Windows script executionNative logs · Draft
Unsafe open() handling exposes a PowerShell command-injection sink.
What to look for
A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Visibility: Defender-side logs where collected
Required logs
- Windows process creation: Sysmon Event 1 or Defender DeviceProcessEvents
- PowerShell script-block logging when enabled
- Download / network and installer events
Coverage limit. Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
Windows process candidates. Sigma uses normalized process_creation fields; KQL requires Defender for Endpoint; SPL requires the Sysmon XML sourcetype. Tune collectors, fields and baselines before use.
Sigma
title: Hunt - Suspicious Windows script execution
id: 2bb88802-9f03-4d99-a192-fe44c9484e8b
status: experimental
description: A script host or shell runs encoded content, a remote URL, or
inline script syntax, then downloads or launches a payload.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- \powershell.exe
- \pwsh.exe
- \mshta.exe
- \wscript.exe
- \cscript.exe
CommandLine|contains:
- -enc
- http
- FromBase64String
- "javascript:"
- "vbscript:"
condition: selection
KQL
// Draft hunt; requires Defender for Endpoint process telemetry for this OS.
DeviceProcessEvents
| where Timestamp > ago(7d)
| where FileName in~ ("powershell.exe", "pwsh.exe", "mshta.exe", "wscript.exe", "cscript.exe")
| where ProcessCommandLine contains "-enc" or ProcessCommandLine contains "http" or ProcessCommandLine contains "FromBase64String" or ProcessCommandLine contains "javascript:" or ProcessCommandLine contains "vbscript:"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA1
| order by Timestamp descSPL
sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
Image IN ("*\\powershell.exe", "*\\pwsh.exe", "*\\mshta.exe", "*\\wscript.exe", "*\\cscript.exe")
CommandLine IN ("*-enc*", "*http*", "*FromBase64String*", "*javascript:*", "*vbscript:*")
| table _time host User Image CommandLine ParentImage ParentCommandLine
| sort - _timeInvestigation steps
- Follow the parent and child process tree and recover the script or URL from logs without executing it.
- Correlate the payload's signer/hash, persistence, and network activity; baseline approved automation.
04Commands execute on the clientSuspicious Windows script executionNative logs · Draft
The report groups openmcp-client with the same OAuth URL execution class.
What to look for
A script host or shell runs encoded content, a remote URL, or inline script syntax, then downloads or launches a payload.
Visibility: Defender-side logs where collected
Required logs
- Windows process creation: Sysmon Event 1 or Defender DeviceProcessEvents
- PowerShell script-block logging when enabled
- Download / network and installer events
Coverage limit. Encoded commands and remote administration can be legitimate. This does not cover every script host, in-process execution, or non-Windows branch.
Windows process candidates. Sigma uses normalized process_creation fields; KQL requires Defender for Endpoint; SPL requires the Sysmon XML sourcetype. Tune collectors, fields and baselines before use.
Sigma
title: Hunt - Suspicious Windows script execution
id: 2bb88802-9f03-4d99-a192-fe44c9484e8b
status: experimental
description: A script host or shell runs encoded content, a remote URL, or
inline script syntax, then downloads or launches a payload.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- \powershell.exe
- \pwsh.exe
- \mshta.exe
- \wscript.exe
- \cscript.exe
CommandLine|contains:
- -enc
- http
- FromBase64String
- "javascript:"
- "vbscript:"
condition: selection
KQL
// Draft hunt; requires Defender for Endpoint process telemetry for this OS.
DeviceProcessEvents
| where Timestamp > ago(7d)
| where FileName in~ ("powershell.exe", "pwsh.exe", "mshta.exe", "wscript.exe", "cscript.exe")
| where ProcessCommandLine contains "-enc" or ProcessCommandLine contains "http" or ProcessCommandLine contains "FromBase64String" or ProcessCommandLine contains "javascript:" or ProcessCommandLine contains "vbscript:"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA1
| order by Timestamp descSPL
sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
Image IN ("*\\powershell.exe", "*\\pwsh.exe", "*\\mshta.exe", "*\\wscript.exe", "*\\cscript.exe")
CommandLine IN ("*-enc*", "*http*", "*FromBase64String*", "*javascript:*", "*vbscript:*")
| table _time host User Image CommandLine ParentImage ParentCommandLine
| sort - _timeInvestigation steps
- Follow the parent and child process tree and recover the script or URL from logs without executing it.
- Correlate the payload's signer/hash, persistence, and network activity; baseline approved automation.
Technical detailsTooling, impact
Attack context
- AI's role
- Agent / MCP as target
Tooling as reported
AI products, models and artifacts
- openmcp-client
- MCP OAuth
Detection rules
- Review attack-specific indicatorsGUIDANCE
Monitor for the techniques described in CVE-2025-58062 openmcp-client open() RCE class. Refer to sources for specific IOCs and TTPs.
Source defensive notes
Upgrade clients; never shell-interpolate remote OAuth URLs
Sources & research credit
1 sourceResearch by Industry CVE assignment · openmcp-client maintainers / NVD
Record & downloads
- Source record name
- CVE-2025-58062 openmcp-client open() RCE class
- Entry ID
- cve-2025-58062-openmcp-client
- Catalog review
- October 20, 2026
- Category
- attacks-on-ai
- AI involvement confidence
- confirmed