Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Power Apps tenant
-
ExploitDeliver malicious origin/content to victim
-
ExecutionBypass origin validation on user interaction
-
ImpactExecute code over network with full impact
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
|
| Exploitation Conditions | Exploitation requires a valid authenticated/authorized identity in the Power Apps environment (PR:L) AND active victim interaction (UI:R) - a legitimate user must interact with attacker-supplied content or a malicious origin for the improper origin validation (CWE-346) to be triggered. Affected deployments are limited to Microsoft Power Apps for Android before 3.26085.7 and Power Apps 1710 (9.2.23071.136) before 2608.5; patched versions are not vulnerable. The authentication prerequisite and the dependency on user interaction are the key limiting factors that reduce realistic risk below what the 8.0 base score alone suggests, and CISA SSVC confirms the attack is not automatable. |
| Impact | This is a genuine elevated-priority issue but not an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 8.0) describes a network-reachable flaw with low attack complexity that nonetheless requires an authenticated/authorized attacker (PR:L) and victim user interaction (UI:R), with total impact to confidentiality, integrity, and availability. These two requirements are corroborated by CISA's SSVC decision, which records Exploitation=none, Automatable=no, and Technical Impact=total - meaning high damage potential but no evidence of active exploitation and no reliable mass-automation path (consistent with the UI:R requirement). No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis. The signals are internally consistent rather than conflicting: high technical impact paired with real exploitation friction (authentication + user interaction + non-automatable). One metadata inconsistency to verify: the input Tag 'Information Disclosure' conflicts with the description and CVSS, which describe code execution with full C/I/A impact (CWE-346 origin validation error), so the tag appears mislabeled and should not drive prioritization. A patch is confirmed available from the vendor, so the practical priority is to deploy the fixed versions promptly rather than to treat this as an actively-exploited zero-day. |
| Exploit ScenarioDerived | An authenticated attacker within a Power Apps tenant crafts content or a malicious origin that abuses the app's improper origin validation, then lures a legitimate user into interacting with it (UI:R). When the victim interacts, the flawed origin check is bypassed and attacker-controlled code executes over the network in the victim's context, yielding high confidentiality, integrity, and availability impact. No public exploit code was identified at time of analysis, and CISA SSVC rates this as not automatable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
An origin validation error (CWE-346) in Microsoft Power Apps allows an authenticated attacker to achieve remote code execution against affected client deployments by inducing a legitimate user to interact with attacker-controlled content. Only Microsoft Power Apps for Android before 3.26085.7 and Power Apps 1710 (9.2.23071.136) before 2608.5 are affected; patched builds are not vulnerable. Exploitation requires a valid authorized identity in the Power Apps environment (PR:L) plus victim interaction (UI:R), CISA's SSVC assessment records no observed exploitation and rates the attack as not automatable, and no public exploit identified at time of analysis; treat this as an elevated-priority but non-emergency patch item.
RemediationAI
Vendor-released patch: Power Apps for Android 3.26085.7 and Power Apps 1710 build 2608.5 (or later) - upgrade mobile and desktop clients to those versions or newer per the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70213, and force update through your MDM/Intune app deployment so that unpatched builds are replaced rather than left alongside the new one. Because exploitation requires an authenticated identity plus user interaction, compensating controls should target both: apply Intune App Protection Policies and Conditional Access so Power Apps can only be used on managed, compliant devices (trade-off: blocks legitimate BYOD access), and restrict or disable embedded/third-party web content and unapproved connectors via Power Platform DLP policies (trade-off: breaks business processes that depend on those connectors). Additional short-term controls include blocking the affected client version ranges from your tenant until devices are updated, monitoring for unusual client-side activity after a user opens untrusted links, and reinforcing user awareness about not opening Power Apps links or content from unverified origins (trade-off: user education is unreliable as a sole control).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an origin validation error (CWE-346) in the Microsoft Power Apps mobile/desktop client. Clients of this type are hybrid applications that render hosted Power Apps content and third-party or embedded web content inside a WebView-style container, and they rely on origin checks to decide whether messages, redirects, or loaded resources come from a trusted Power Apps origin. When those checks are insufficient, an attacker-controlled page or malicious origin can be treated as trusted, breaking the intended trust boundary between the trusted application context and untrusted web content and enabling code execution within the client's privileged context. The affected CPE/version data identifies the vulnerable components as Microsoft Power Apps for Android (versions 1.0.0 through below 3.26085.7) and the Power Apps 1710 build line (9.2.23071.136 through below 2608.5), confirming this is a client-side validation defect rather than a service-side issue with the Power Platform backend. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H indicates the attack is network-reachable, requires authenticated access, requires victim interaction, does not cross a privilege boundary, and produces high confidentiality, integrity, and availability impact once triggered.
Know when Android 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:L/UI:R/S:U/C:H/I:H/A:H
Network-reachable (AV:N) with low complexity, but requires an authorized attacker (PR:L) and victim interaction (UI:R); origin-validation bypass yields full code execution, so C/I/A are all High.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Origin validation error in Microsoft Power Apps allows an authorized attacker to execute code over a network.
Articles & Coverage 1
Executive ViewAI
Unpatched Microsoft Power Apps mobile clients allow an attacker who already holds valid credentials in the organization's Power Apps environment to execute remote code on a user's device after convincing that user to interact with attacker-controlled content. Because these clients are the same endpoints employees use to reach business applications and corporate data, a successful attack could compromise the device and the information accessible from it. With no observed exploitation, no public exploit identified at time of analysis, and vendor fixes available, this is an elevated-priority patch item rather than an emergency.
Apply vendor patch.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-99610
GHSA-jxmh-w5xx-jqc7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB