Python StatemachineApplication · Fgmacedo
CVE-2026-47103
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPython 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePython StateMachine versions 3.0.0-3.1.x contain an RCE vulnerability where the SCXMLProcessor evaluates attacker-controlled expressions from `<data expr='...'>` attributes through Python's built-in eval() without any sandboxing, allowing arbitrary code execution in the hosting process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Python StatemachineApplication
>= 3.0.0, < 3.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed statemachine package versionRun `pip show statemachine` or `python -c "import statemachine; print(statemachine.__version__)"` to identify the installed versionAffected if The version is 3.0.0 through 3.1.x (any version >= 3.0.0 and < 3.2.0)
-
Verify SCXMLProcessor is in useSearch your codebase for imports or usage of SCXMLProcessor, for example: `grep -r "SCXMLProcessor" .` or `grep -r "from statemachine" .`Affected if Your code imports or uses SCXMLProcessor from the statemachine library
-
Identify SCXML document processingSearch for code that loads or parses SCXML files, for example: `grep -r "\.scxml" .` or look for patterns like `parse_SCXML` or `SCXMLParser`Affected if Your application loads, parses, or processes SCXML documents from any source
-
Locate SCXML files with data expr attributesInspect any SCXML files in your project or input data: search for `<data expr="` patterns which indicate the vulnerable attribute is presentAffected if SCXML documents contain `<data expr="...">` elements with attacker-controlled expressions
You are affected if you have statemachine version 3.0.0-3.1.x AND your code uses SCXMLProcessor to process SCXML documents containing `<data expr="...">` attributes, especially from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.2.0
Upgrade to StateMachine version 3.2.0 or later which addresses the unsafe eval() usage; until then, do not process untrusted SCXML documents with the affected library.
python-statemachine >= 3.2.0
- Upgrade python-statemachine to version 3.2.0 or later using pip: pip install python-statemachine>=3.2.0
- Verify the installed version: pip show python-statemachine
- Test that SCXML processing functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Python Statemachine
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47103 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47103 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data