# CVE-2026-47103: Python StateMachine 3.0.0 < 3.2.0 RCE via SCXML eval() Injection

> Attackers can execute arbitrary code by providing malicious SCXML documents to the Python StateMachine library due to unsafe eval() usage.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jun 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-v4jc-pm6r-3vj8, PYSEC-2026-506

## What is CVE-2026-47103?

CVE-2026-47103 is a critical code injection vulnerability in fgmacedo python-statemachine, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Python StateMachine versions 3.0.0 before 3.2.0 contains a remote code execution vulnerability that allows attackers to execute arbitrary code by supplying malicious SCXML documents containing crafted `<data expr="...">` attributes evaluated unsafely. The SCXMLProcessor passes attacker-controlled expression strings through a call chain ending in Python's built-in eval() without sandboxing, enabling arbitrary code execution in the context of the hosting process.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

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

3 open source packages ship an affected version, including python-statemachine. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-statemachine` | PyPI | From 3.0.0 | 3.2.0 |
| `python-statemachine` | PyPI | From 3.0.0 | 3.2.0 |
| `python-statemachine` | PyPI | From 3.0.0 | 3.2.0 |

Products: Fgmacedo Python Statemachine.

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

Upgrade python-statemachine to 3.2.0 or later.

## Is CVE-2026-47103 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47103 exists.

Public exploit code:

- Python StateMachine 3.0.0 < 3.2.0 RCE via unsafe SCXML <data expr> evaluation and Python eval() injection. (github_poc): https://github.com/SaiTeja-Erukude/CVE-2026-47103-python-statemachine-rce

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47103 is a critical code injection vulnerability in fgmacedo python-statemachine, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47103 exists.

Affected packages and fixed versions:
- python-statemachine (PyPI): affected from 3.0.0; fixed in 3.2.0
- python-statemachine (PyPI): affected from 3.0.0; fixed in 3.2.0
- python-statemachine (PyPI): affected from 3.0.0; fixed in 3.2.0

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-47103/ (Markdown: https://insights.sbomify.com/CVE-2026-47103/index.md)
```

## Sources

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

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