AWS virtual-engineering-workbench
Template injection in the publishing component of awslabs Virtual Engineering Workbench
Improper neutralization of special elements used in a template engine in the publishing component of Amazon Virtual Engineering Workbench (VEW) could allow a remote authenticated third party to run arbitrary code with the permissions of the publishing Lambda's IAM role. This could allow access to data and resources across all tenant projects. The code is reachable through a crafted CloudFormation template body containing template engine directives submitted through the product versioning API. To remediate this issue, users should redeploy from the latest version of awslabs/virtual-engineering-workbench.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < c146486cec41f5b04fae57e9ce1a7fb40e695615
Fixed in c146486cec41f5b04fae57e9ce1a7fb40e695615
Mitigation
Upgrade virtual-engineering-workbench to c146486cec41f5b04fae57e9ce1a7fb40e695615 or later.
References
- Patch github.com/awslabs/virtual-engineering-workben…
- Vendor advisory aws.amazon.com/security/security-bulletins/2026-16…
- Vendor advisory github.com/awslabs/virtual-engineering-workben…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.