CVE-2026-47103

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.4% (71st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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 `` 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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
71st
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 17, 2026

Last Modified

October 8, 2026

Advisory Details (4)

Auto-updated Oct 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

python-statemachine SCXML <data expr> Eval Injection · Advisory · fgmacedo/python-statemachine · GitHub

https://github.com/fgmacedo/python-statemachine/security/advisories/GHSA-v4jc-pm6r-3vj8
generic

Python StateMachine 3.0.0 < 3.2.0 RCE via SCXML eval() Injection | Advisories | VulnCheck

https://www.vulncheck.com/advisories/python-statemachine-rce-via-scxml-eval-injection
github_release Patch Available

v3.2.0

Patch available: fgmacedo/python-statemachine v3.2.0

https://github.com/fgmacedo/python-statemachine/releases/tag/v3.2.0
generic🟡 PoC Available

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

https://github.com/SaiTeja-Erukude/CVE-2026-47103-python-statemachine-rce

Vendor Advisories for CVE-2026-47103(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
python-statemachine3.0.0, 3.1.0, 3.1.1, 3.1.2
  • 3.0.0 up to 3.2.0: fixed in 3.2.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-08 16:40 UTCEG score recompute
  4. 2026-10-08 15:46 UTCEG score recompute
  5. 2026-10-07 23:48 UTCEPSS rescore
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-03 15:19 UTCOSV refresh
  10. 2026-10-03 14:25 UTCEPSS rescore
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-09-30 15:03 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-26 00:27 UTCEPSS rescore
  17. 2026-09-23 17:53 UTCEPSS rescore
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-14 02:25 UTCEG score recompute
  23. 2026-09-13 16:47 UTCEPSS rescore
  24. 2026-09-13 14:14 UTCEG score recompute
  25. 2026-09-12 15:01 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 14:12 UTCEPSS rescore
  9. 2026-09-01 13:54 UTCEPSS rescore
  10. 2026-08-30 21:21 UTCEG score recompute
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 23:48 UTCEG score recompute
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 22:25 UTCEG score recompute
  19. 2026-08-23 04:21 UTCEG score recompute
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:58 UTCEG score recompute
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 02:08 UTCEG score recompute
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 08:14 UTCEG score recompute
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-19 08:10 UTCEG score recompute
  28. 2026-08-18 13:48 UTCEPSS rescore
  29. 2026-08-17 14:57 UTCEG score recompute
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-16 16:00 UTCEG score recompute
  32. 2026-08-16 14:56 UTCEPSS rescore
  33. 2026-08-16 02:55 UTCEG score recompute
  34. 2026-08-16 02:14 UTCEPSS rescore
  35. 2026-08-15 02:12 UTCEG score recompute
  36. 2026-08-15 01:30 UTCEPSS rescore
  37. 2026-08-13 23:42 UTCEG score recompute
  38. 2026-08-13 22:00 UTCEPSS rescore
  39. 2026-08-12 18:06 UTCEG score recompute
  40. 2026-08-12 13:51 UTCEPSS rescore
  41. 2026-08-11 15:23 UTCEG score recompute
  42. 2026-08-11 02:18 UTCEG score recompute
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-09 13:56 UTCEG score recompute
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-08 20:29 UTCEG score recompute
  47. 2026-08-08 16:37 UTCEPSS rescore
  48. 2026-08-07 18:19 UTCEG score recompute
  49. 2026-08-06 16:09 UTCEG score recompute
  50. 2026-08-06 13:47 UTCEPSS rescore
  51. 2026-08-05 22:40 UTCEG score recompute
  52. 2026-08-05 19:17 UTCEPSS rescore
  53. 2026-08-04 15:26 UTCEG score recompute
  54. 2026-08-04 15:10 UTCEPSS rescore
  55. 2026-08-04 10:39 UTCEPSS rescore
  56. 2026-08-03 14:25 UTCEG score recompute
  57. 2026-08-03 10:36 UTCEPSS rescore
  58. 2026-08-02 03:12 UTCEG score recompute
  59. 2026-08-02 02:27 UTCEPSS rescore
  60. 2026-08-01 05:22 UTCEG score recompute
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-30 22:39 UTCEG score recompute
  63. 2026-07-30 16:28 UTCEPSS rescore
  64. 2026-07-30 03:38 UTCEG score recompute
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-29 02:09 UTCEG score recompute
  67. 2026-07-28 15:37 UTCEPSS rescore
  68. 2026-07-27 18:09 UTCEG score recompute
  69. 2026-07-27 14:13 UTCEPSS rescore
  70. 2026-07-26 19:08 UTCEG score recompute
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-24 14:17 UTCEPSS rescore
  75. 2026-07-23 14:18 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47103?
CVE-2026-47103 is a critical vulnerability published on June 17, 2026. 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…
When was CVE-2026-47103 disclosed?
CVE-2026-47103 was first published on June 17, 2026, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47103 actively exploited?
CVE-2026-47103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (71st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47103?
CVE-2026-47103 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47103?
A fix for CVE-2026-47103 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47103 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47103

Explore →

Is Your Infrastructure Affected by CVE-2026-47103?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs