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: 0.8%, top 48% of all CVEs by exploit prediction. 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
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.8(medium)
EPSS
52.2%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 18, 2026

Advisory Details (3)

Auto-updated Jun 29, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 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

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 rangeFixed inDependents
python-statemachine3.0.0, 3.1.0, 3.1.1, 3.1.23.2.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 43× in last 7d / 133× 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 133 total refreshes for this CVE.

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

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 in the National Vulnerability Database on June 17, 2026, with the most recent update on June 18, 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 52.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47103?
CVE-2026-47103 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-47103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47103, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs