{"answers":{"affected":"3 open source packages ship an affected version, including python-statemachine. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47103 exists.","fix":"Upgrade python-statemachine to 3.2.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-47103 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47103 exists.\n\nAffected packages and fixed versions:\n- python-statemachine (PyPI): affected from 3.0.0; fixed in 3.2.0\n- python-statemachine (PyPI): affected from 3.0.0; fixed in 3.2.0\n- python-statemachine (PyPI): affected from 3.0.0; fixed in 3.2.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47103/ (Markdown: https://insights.sbomify.com/CVE-2026-47103/index.md)","id":"CVE-2026-47103","markdown":"https://insights.sbomify.com/CVE-2026-47103/index.md","name":"CVE-2026-47103","record":{"aliases":["GHSA-v4jc-pm6r-3vj8","PYSEC-2026-506"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python state machine library","requires_auth":"none","summary":"Attackers can execute arbitrary code by providing malicious SCXML documents to the Python StateMachine library due to unsafe eval() usage.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"python_statemachine","vendor":"fgmacedo"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"}],"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 `\u003cdata expr=\"...\"\u003e` 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2026-08-15","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-15T21:25:54Z","kind":"github_poc","ref":"https://github.com/SaiTeja-Erukude/CVE-2026-47103-python-statemachine-rce","stars":0,"title":"Python StateMachine 3.0.0 \u003c 3.2.0 RCE via unsafe SCXML \u003cdata expr\u003e evaluation and Python eval() injection."}],"tier":"weaponised"},"has_fix":true,"headline":"Python StateMachine 3.0.0 \u003c 3.2.0 RCE via SCXML eval() Injection","id":"CVE-2026-47103","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"libusb \u003c 1.0.30 Out-of-Bounds Read in parse_iad_array()","id":"CVE-2026-47104"},"packages":[{"ecosystem":"PyPI","fixed":["3.2.0"],"introduced":["3.0.0"],"last_affected":[],"package":"python-statemachine","purl":null,"source":"GHSA-v4jc-pm6r-3vj8"},{"ecosystem":"PyPI","fixed":["3.2.0"],"introduced":["3.0.0"],"last_affected":[],"package":"python-statemachine","purl":"pkg:pypi/python-statemachine","source":"GHSA-v4jc-pm6r-3vj8"},{"ecosystem":"PyPI","fixed":["3.2.0"],"introduced":["3.0.0"],"last_affected":[],"package":"python-statemachine","purl":"pkg:pypi/python-statemachine","source":"PYSEC-2026-506"}],"prev":{"headline":"LiteLLM \u003c 1.83.10 Privilege Escalation via User Update","id":"CVE-2026-47102"},"products":["python-statemachine"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["fgmacedo"]},"summary":"Attackers can execute arbitrary code by providing malicious SCXML documents to the Python StateMachine library due to unsafe eval() usage.","url":"https://insights.sbomify.com/CVE-2026-47103/"}