CVE-2026-89065
CVE-2026-89065 — Relative path traversal in the generated file manifest cleanup component in projen
Relative path traversal in the generated file manifest cleanup component in projen before 0.101.37 might allow context-dependent attackers to recursively delete files and directories outside the project directory that are writable by the environment running projen, via crafted entries in the version-controlled generated file manifest that is consumed during project synthesis. To remediate this issue, users should upgrade to version 0.101.37. The corrected containment check is automatically applied by the projen runtime next time you run it.
Published Updated Sources: NVD, AWS (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7.1
high · 2 sources
Remediation
The vendor's own words where we have them.
Upgrade projen to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| AWS | projen | 0 to < 0.101.37 | Vulnerable |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
High
Confidentiality
None
Integrity
High
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Local
Privileges Req
None
User Interaction
Required
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.1 | CVSS 3.1 | high | 1.8 | 5.2 | CNA, AWS (CNA) |
| 6.8 | CVSS 4.0 | medium | — | — | AWS (CNA) |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
Weakness & attack patterns
- CWE-23
Inferred from the weakness class — not observed against this CVE.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 7.1 (AV:L)
Sep 11, 2026 · NVD
Initial · CVE published
Sep 11, 2026 · NVD
References
3 on the record
- aws.amazon.com/security/security-bulletins/2026-108-aws/
Vendor Advisory
- github.com/projen/projen/releases/tag/v0.101.37
Exploit, Third Party Advisory
- github.com/projen/projen/security/advisories/GHSA-7p65-6x86-v7f3
Exploit, Third Party Advisory
Elsewhere on this site
- AWSevery CVE for this vendor
- Path Traversalsame class
- CWE-23other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-89065 is Relative path traversal in the generated file manifest cleanup component in projen, a high vulnerability affecting projen from AWS. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-89065. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-89065. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.