CVE-2026-108263
Astron Agent code injection
- Published9 Oct 2026
Description
Astron Agent is an agentic workflow platform for building and running AI agents. Prior to 1.1.2, the default workflow code-node path through /console-api/workflow/code/run and /workflow/v1/run selects LocalExecutor in core/workflow/engine/nodes/code/code_node.py when CODE_EXEC_TYPE is not explicitly changed. LocalExecutor supplies complete Python builtins to dynamic code execution without the documented sandbox restrictions. An authenticated low-privilege tenant can execute code as root in the core-workflow container and use shared service and database credentials to bypass application-level tenant checks, read or modify other tenants' data, and disrupt shared services. This issue is fixed in version 1.1.2.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HRemediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/iflytek/astron-agent/commit/848daba03e5e045435863815be7ab6dfbcefc18f
- https://github.com/iflytek/astron-agent/commit/ebf074a431e96da0ad9e0a56409d3d2da15eae36
- https://github.com/iflytek/astron-agent/pull/1650
- https://github.com/iflytek/astron-agent/pull/1651
- https://github.com/iflytek/astron-agent/releases/tag/v1.1.2
- https://github.com/iflytek/astron-agent/security/advisories/GHSA-mh3w-4q3f-2fg5
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-108263 being actively exploited?
CVE-2026-108263 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.43%.
How severe is CVE-2026-108263?
CVE-2026-108263 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 0.43% probability of exploitation.
How do I fix CVE-2026-108263?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-108263 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.