Skip to content

Astron Agent v1.1.2 — Security Release

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Sep 06:43
v1.1.2
189600d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Security Release

Astron Agent v1.1.2 is a security release. Operators running v1.1.1 or earlier should upgrade promptly, especially those running multi-tenant deployments.

Workflow code execution and tenant isolation

This release addresses unsafe workflow code-node execution that could allow an authenticated user with workflow creation permissions to execute code in the workflow service container and access or modify other tenants' data in affected deployments.

  • Affected versions: <= v1.1.1, when using the legacy unsandboxed local code executor. Single-tenant deployments are also affected by the code-execution risk.
  • Patched version: v1.1.2.
  • Related advisory: GHSA-mh3w-4q3f-2fg5. The security advisory is now public. A CVE identifier has been requested from GitHub and is awaiting assignment.

The release includes the executor migration in #1650, integrated into main through #1651, together with the preceding security hardening:

  • Reject unsafe local code execution and use the built-in isolated LangChain/Pyodide executor by default; E2B remains optional.
  • Migrate untouched legacy executor configuration while preserving explicit process-level overrides, including intentional disabling of code nodes.
  • Strengthen authentication on internal Workflow and Tenant service APIs, tenant checks, credential handling, and deployment isolation.

Additional security fixes

  • Prevent server-side request forgery (SSRF) in outbound plugin requests (#1669).
  • Harden XSS, artifact and sandbox boundaries, and scope CSRF exclusions (#1643).

Upgrade Notes

  1. Back up your databases, persistent data, and deployment configuration before upgrading.
  2. Update the deployment files and service images together. Use the Compose, service configuration, and gateway configuration shipped with this release, merging your site-specific settings. Updating only the source checkout or only the workflow image does not apply the complete fix.
  3. For Docker Compose deployments, set ASTRON_AGENT_VERSION=v1.1.2 in docker/astronAgent/.env, pull the updated service images, and recreate the stack. Then verify service health and workflow code-node execution. Automated vulnerability scanners may not flag this application-level issue; operators should verify the deployed image versions explicitly.
  4. Review custom code-executor overrides. CODE_EXEC_TYPE=local is no longer supported; use the default isolated executor or a supported remote executor. Code that depends on host filesystem, environment, subprocess, or network access may need adaptation to the isolated runtime.

Container images: The v1.1.2 release workflow successfully built and pushed all eight core service images, Console Hub, and Console Frontend to GHCR with the v1.1.2 tag for linux/amd64 and linux/arm64. These images correspond to release commit 189600dd691e8562bd0b9f7112727b107b8a2e10. Use the explicit release tag for this upgrade; record or pin image digests for reproducibility.

See the release's deployment guide and configuration reference for deployment requirements and executor migration details.

Other Changes

  • Add Langfuse integration and end-to-end agent traces (#1607).
  • Harden dependency-aware workflow YAML imports (#1623).
  • Improve image-build reliability with a reliable PyPI source for RPA and retries for Maven Central rate limits (#1660).
  • Fix documentation preview assets and the Japanese README image path (#1653, #1655).

Acknowledgements

Thank you to Noy Pearl and the Lasso Security team for responsibly reporting the workflow code-execution issue, collaborating on remediation, and re-testing the fix.

Full changelog: v1.1.1...v1.1.2

Assets 2
Loading