Command Injection Affecting projen package, versions <0.103.0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-PROJEN-19823705
- published15 Sept 2026
- disclosed11 Sept 2026
- creditEthanMiller
Introduced: 11 Sep 2026
NewCVE-2026-89066 (opens in a new tab)How to fix?
Upgrade projen to version 0.103.0 or higher.
Overview
projen is a CDK for software projects
Affected versions of this package are vulnerable to Command Injection in the task synthesis, which interpolates configuration properties and auto-discovered file names into the generated .projen/tasks.json without escaping shell metacharacters, affecting properties including extraArgs, testMatch, entrypoint, registryUrl, and distdir. An attacker who can influence project configuration or repository file names, as a contributor or by adding a file whose name carries shell metacharacters such as ;, &&, $(...), or backticks, can execute commands with the filesystem access and secrets of a developer workstation or CI runner. This requires the ability to modify configuration or contribute files, and execution occurs when an affected task runs, which spans the project lifecycle from test and eslint through release and publish:*.
Note: The project maintainers advise that "After upgrading, you must re-synthesize your project to regenerate .projen/tasks.json with the corrected task definitions."