Template injection in the publishing component of awslabs Virtual Engineering Workbench
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects all commits before c146486 (PR #31) Triggered by a crafted CloudFormation template body with template engine directives submitted through the product versioning API
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fix or patch referenced
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The publishing component of the awslabs Virtual Engineering Workbench, an Amazon tool for managing engineering environments, is affected by this vulnerability. A remote, authenticated attacker could exploit it by submitting a crafted template through the product versioning API to run arbitrary code, potentially accessing data and resources across all tenant projects.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
Affects all commits before c146486 (PR #31) Triggered by a crafted CloudFormation template body with template engine directives submitted through the product versioning APIApply the patch listed under Evidence.
Workaround: Limit which users can create or update product versions until redeployed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- AWS virtual-engineering-workbench
Version range not reported
Evidence 2
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119085
What does this mean?
A crafted CloudFormation template body containing template engine directives can make the product's publishing component run attacker-chosen code. The code then runs with the permissions of the publishing Lambda's IAM role, which can reach data and resources across all tenant projects.Source: aws.amazon.com
Am I affected, and how do I check?
The advisory says versions before commit c146486 (PR #31, merged 2026-05-04) are affected, and the product's version range list is empty. Check whether your deployment includes that commit, or whether the product versioning API accepts CloudFormation template bodies with template engine directives.Source: aws.amazon.com
What should I do about it?
Update to a build that includes commit c146486 (PR #31), which the advisory says addresses the issue. No separate patched version number is listed in the facts.Source: aws.amazon.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data