Astron Agent v1.1.2 deprecates legacy code executor

The Astron Agent v1.1.2 release, as detailed in the project's GitHub release notes, addresses critical security vulnerabilities affecting versions v1.1.1 and earlier. These include unsafe workflow code-node execution risks that could allow authenticated users with workflow creation permissions to execute arbitrary code within the workflow service container, potentially compromising tenant isolation in multi-tenant deployments. Single-tenant deployments are also affected by the code-execution risk. This release replaces the legacy unsandboxed local code executor with a default isolated LangChain/Pyodide executor, while retaining optional support for E2B.

Operators must note that the legacy local executor configuration is deprecated and no longer supported, requiring migration to the isolated runtime or a supported remote executor. Any custom code relying on host filesystem, environment variables, subprocesses, or network access may need adaptation to function within the new isolated runtime. Before upgrading, operators should review deployment configurations, back up databases and persistent data, and ensure that all service images are updated together to apply the complete fix. Partial upgrades, such as updating only the source checkout or workflow image, will not address the vulnerabilities.

Additionally, operators should verify service health and workflow code-node execution after upgrading, as automated vulnerability scanners may not flag these application-level issues. Explicitly pinning image digests for reproducibility is recommended. This release also strengthens authentication for internal APIs, tenant checks, and credential handling, while addressing SSRF, XSS, and CSRF risks. Operators should carefully review the release's deployment guide and configuration reference to ensure compliance with the new runtime requirements.