Live › vulnerability › CVE-2026-119085
Virtual Engineering Workbench's publishing component fails to neutralize template directives in CloudFormation template bodies submitted through the product versioning API. An authenticated remote user can run arbitrary code with the publishing Lambda's IAM role, reaching data and resources across tenant projects.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-02 18:03 UTC, 0h before NVD. All times on this page are UTC.
Teams that self-host or deploy Amazon Virtual Engineering Workbench, where platform engineers publish development environments and developers provision them through a web portal. Builds from commit c146486 or later, and deployments that do not let untrusted users create or update product versions, are not affected by the reported flaw. Forks and derivatives carry the bug until they incorporate the fix.
No product ranges from the sources yet.
c146486 (PR #31, merged 2026-05-04) or later.c146486.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-119085 - Template injection in the publishing component of Virtual Engineering Workbench
Bulletin ID: 2026-162-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/02/2026 09:30 AM PST
Description:
Virtual Engineering Workbench (VEW) is an open-source platform where platform engineers define and publish development environments, and developers provision them on demand through a web portal. We identified CVE-2026-119085, where 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.
Impacted versions: All commits before c146486 (PR #31, merged 2026-05-04)
Resolution:
This issue has been addressed in commit c146486 (PR #31). We recommend redeploying from the latest version of the main branch and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds:
There is no workaround that removes the issue. Until you redeploy, you can reduce impact by limiting which users can create or update product versions.
References:
Acknowledgement:
We would like to thank Trung Nguyen of CyStack for collaborating on this issue through the coordinated vulnerability disclosure process.
Please email [email protected] with any security questions or concerns.
This page as .md · .json · in your agent: get_signal("CVE-2026-119085")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.