Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Logic Apps endpoint over network
-
DeliverySend request with path-traversal sequences
-
ExploitEscape restricted directory
-
ExecutionAccess out-of-scope resources
-
ImpactElevate privileges / full compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Per the CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication or user interaction is required and the attack is network-reachable against Azure Logic Apps. The description specifies path traversal ('improper limitation of a pathname to a restricted directory') as the mechanism, but Microsoft's advisory does not name the specific endpoint, feature, or configuration that must be reachable, so the exact triggering surface is not documented. The principal limiting factor is that Azure Logic Apps is a Microsoft-managed cloud service: remediation is applied centrally by Microsoft rather than by customers, so tenant exposure depends on whether the service instance predates Microsoft's fix rather than on any customer-side setting. |
| Impact | Signals are mixed. The CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N with C:H/I:H/A:H) describes an unauthenticated, network-reachable, low-complexity flaw with total impact, and CISA's SSVC concurs that technical impact is 'total' and the flaw is 'automatable: yes' - both worst-case indicators. However, the SSVC 'Exploitation: none' rating, absence from CISA KEV, no known public POC, and a modest EPSS of 0.58% (47th percentile) all indicate there is no evidence of real-world exploitation and only middling predicted likelihood. A critical mitigating factor not reflected in the raw score: Azure Logic Apps is a Microsoft-operated cloud (PaaS) service, so the fix is deployed centrally by Microsoft rather than requiring customer patching - meaning the practical window of exposure for tenants is largely closed once Microsoft remediates. There is also a semantic tension to verify: the description frames this as a privilege-elevation ('elevate privileges over a network') while the CVSS vector encodes it as fully unauthenticated (PR:N) with total CIA loss, which reads more like remote takeover than classic EoP - Microsoft's advisory is sparse and does not resolve this. Net: high theoretical severity, but as a centrally-patched cloud service with no exploitation evidence this is a lower operational priority for most defenders than the 9.8 implies. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends crafted requests containing directory-traversal sequences to an Azure Logic Apps endpoint, escaping the intended restricted directory to access or manipulate resources outside its scope and thereby gain elevated privileges over the service. Because CVSS marks AV:N/AC:L/PR:N/UI:N and SSVC marks the attack automatable, the request could be scripted at scale. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Sep 25, 2026
Path traversal in Microsoft's Azure Logic Apps (CWE-22) lets a remote, unauthenticated attacker escape an intended restricted directory and elevate privileges over the network, with the vendor's CVSS 9.8 score reflecting high confidentiality, integrity, and availability impact under a PR:N/UI:N vector. The defect affects the hosted Azure Logic Apps service rather than a versioned on-premises component, and Microsoft's advisory does not disclose the specific endpoint, feature, or configuration that must be reachable, so the precise triggering surface remains undocumented. No public exploit code has been identified and CISA's SSVC assessment records no observed exploitation (Exploitation: none) while flagging the issue as automatable with total technical impact; EPSS sits at 0.58% (47th percentile), indicating low modeled near-term exploitation likelihood despite the critical base score. Because Logic Apps is a Microsoft-managed cloud service, exposure depends on whether a given tenant region or service instance was remediated centrally rather than on any customer-side patch action.
Earlier versions of this analysis (1)
Path traversal (CWE-22) in Azure Logic Apps allows an unauthenticated, network-reachable attacker to escape the intended directory restriction and elevate privileges, yielding high confidentiality and integrity impact with no availability impact under a scope-changed CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N). Because Azure Logic Apps is a Microsoft-operated PaaS service, the affected surface is the hosted platform itself rather than a customer-installed binary, so exposure is bounded to the window before Microsoft's server-side fix plus any self-hosted or hybrid Logic Apps runtime that shares the vulnerable code path. No public exploit code or confirmed active exploitation has been identified at time of analysis, and no EPSS score was supplied with the available intelligence.
RemediationAI
Patch status is "Patch available per vendor advisory": Microsoft tracks CVE-2026-70200 through its Security Update Guide, and because Azure Logic Apps is a Microsoft-managed cloud service the fix is deployed centrally by Microsoft rather than installed by customers, so the primary action is to confirm with the vendor advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70200) that the relevant region or service instance has received the remediation and to monitor the MSRC entry or Azure Service Health for deployment status; no customer-installable fix version is identified in the available data. Where the specific vulnerable endpoint is not documented, apply compensating controls on any Logic Apps HTTP request trigger that is anonymously reachable, since the vulnerability requires no authentication: require authentication on request triggers (managed identity, OAuth, or SAS with tightened policies) and disable anonymous access where not strictly needed, accepting that authenticated callers must be updated or integrations will break; apply inbound IP restrictions or private endpoint/VNet integration so only expected networks can reach trigger URLs, at the cost of blocking legitimate external callers and requiring network reconfiguration; rotate any exposure-prone SAS keys and workflow trigger URLs. Reduce automatable exploit paths by disabling unused HTTP triggers and connectors that accept external input, and enable diagnostic logging with Azure Monitor on Logic Apps runs, scanning request URIs for traversal patterns ("../", "..%2f", and double-encoded variants) to detect probing; note that logs and Defender for Cloud alerts are detective, not preventive, controls. Apply the same authentication and network restrictions to API connections and connectors that accept externally supplied paths, weighing each against the operational disruption of hardened integration endpoints.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-22, improper limitation of a pathname to a restricted directory: user-influenced path input reaches file or resource resolution without adequate canonicalization, normalization, or boundary checks, allowing traversal sequences to resolve outside the intended directory. In Azure Logic Apps, a cloud integration-platform-as-a-service (iPaaS) environment where workflows, triggers, and connectors process externally supplied requests, that failure means an attacker can direct resource access across a trust boundary and, per Microsoft's own scoring, elevate privileges and affect confidentiality, integrity, and availability, all with scope unchanged (S:U). The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N confirms the attack is network-reachable with low complexity, requires no credentials and no user interaction, which places the flaw on a pre-authentication surface. The CPE entry cpe:2.3:a:microsoft:azure_logic_apps:-:*:*:*:*:*:*:* carries no version field, consistent with a continuously updated, Microsoft-operated cloud service tracked by ENISA as EUVD-2026-82592 with the placeholder affected version "Azure Logic Apps -". Microsoft's advisory does not name the endpoint or workflow feature exercised by the traversal, so the exact request path needed to reach the vulnerable code is not publicly documented; the practical limiting factor is that remediation is applied centrally by the vendor rather than by customers.
Know when Azure gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vector accepts Microsoft's AV:N/AC:L/PR:N/UI:N and total impact given SSVC 'technical impact: total'; scope kept Unchanged absent evidence of cross-system impact, though sparse advisory limits certainty.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
Improper limitation of a pathname to a restricted directory ('path traversal') in Azure Logic Apps allows an unauthorized attacker to elevate privileges over a network.
Executive ViewAI
A critical path traversal vulnerability in Microsoft's hosted Azure Logic Apps service could let an unauthenticated attacker escape restricted directories and gain elevated network privileges, potentially compromising tenant workflows and connected data. Because this is a Microsoft-managed cloud service, exposure varies by tenant configuration, and no public exploit identified at time of analysis. Leadership should care because Logic Apps often orchestrates sensitive business processes, so any compromise could disrupt operations and expose data even without confirmed active exploitation.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to Logic Apps endpoints via Azure Private Link, IP restrictions, or trusted network policies; enforce least privilege on managed identities, API connections, and service principals; enable and monitor Azure Monitor and Logic Apps diagnostic logs for path traversal or anomalous privilege activity; disable or isolate non-essential workflows and connectors; monitor Microsoft's advisory for service-side updates.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Privilege escalation in Microsoft's Azure Billing service allows unauthenticated, remote attackers to reach full comprom
Path traversal in pnpm's tarball extraction on Windows allows attackers to write files outside the intended package dire
Default password in Himmelblau Azure Entra ID suite 3.0.0-3.0.x. CVSS 10.0.
Privilege escalation in Azure Database for PostgreSQL allows an authenticated attacker with low privileges to elevate pr
Default credentials in Cisco ISE cloud deployments on AWS/Azure/OCI. CVSS 9.9.
Unauthenticated remote attackers can reach a critical function inside Microsoft Azure AI Foundry that performs a privile
Deserialization of untrusted data in Azure SDK allows unauthorized code execution over a network. EPSS 0.32%.
Elevation of privilege vulnerability in Azure Front Door allows attackers to gain elevated access. Microsoft Azure cloud
Azure Front Door has an improper access control vulnerability (CVSS 9.8) allowing unauthorized attackers to elevate priv
Azure AD auth bypass in Devolutions Server 2025.3.15.0 and earlier.
Fleet device management software has a signature verification bypass that allows attackers to install malicious firmware
Privilege elevation in Microsoft Azure Cosmos DB allows an attacker who already holds valid low-level authorization to a
EUVD-2026-82592
GHSA-j33w-4pg5-pvc7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB