# CVE-2026-70213: Microsoft Power Apps Remote Code Execution Vulnerability

> An origin validation error in Microsoft Power Apps for Android allows an authorized attacker to execute code over a network.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-jxmh-w5xx-jqc7

## What is CVE-2026-70213?

CVE-2026-70213 is a high-severity vulnerability in Microsoft Power Apps for Android, published on 13 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Origin validation error in Microsoft Power Apps allows an authorized attacker to execute code over a network.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-70213?


## How do I fix CVE-2026-70213?

No fix has been published for CVE-2026-70213 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70213 being exploited?

There is no known exploitation of CVE-2026-70213 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70213 and fix it if it is affected.

What it is: CVE-2026-70213 is a high-severity vulnerability in Microsoft Power Apps for Android, published on 13 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-70213 in the wild and no public exploit code.

Affected product: Microsoft Power Apps for Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-70213/ (Markdown: https://insights.sbomify.com/CVE-2026-70213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70213
- OSV: https://osv.dev/vulnerability/CVE-2026-70213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70213/
Summaries are generated and may contain mistakes; the official description above is the record.