Skip to main content
VulnerabilityPublished

CVE-2026-89066: AWS projen · OS Command Injection

Affects AWS projenSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High : upgrade to 0.103.0 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.103.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade AWS projen to 0.103.0.

Affected software

ProductAffectedFixed in
AWSprojenAffected
  • <0.103.0
Fixed in
  • 0.103.0
npmprojenpkg:npm/projenOther threatsAffected
  • <0.103.0
Fixed in
  • 0.103.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available. Users must upgrade AWS projen to version 0.103.0 and then re-synthesize their projects to regenerate the .projen/tasks.json file with corrected task definitions. Simply upgrading the software without re-synthesizing the project is insufficient because the vulnerable task definition file is committed to the repository. Follow the vendor advisory at https://aws.amazon.com/security/security-bulletins/2026-108-aws/ for detailed remediation instructions.

Description

Improper neutralization of special elements used in an OS command in the task synthesis component in projen before 0.103.0 might allow context-dependent attackers to execute arbitrary commands on a developer workstation or continuous integration runner via shell metacharacters in project configuration values and repository file names that are interpolated into generated task definitions. To remediate this issue, users should upgrade to version 0.103.0 and then re-synthesize the project so that .projen/tasks.json is regenerated with the corrected task definitions. Upgrading alone is not sufficient because the generated task definition file is committed to the repository.

References

Community reviews

Loading reviews…