Vulnerability in yeoman-environment (CVE-2026-42089)
Summary
Vulnerability in yeoman-environment (CVE-2026-42089). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 6.0.1 or later.
Original description
The description as published by the source.
Impact
yeoman-environment versions >= 2.9.0 and < 6.0.1 install missing local generator packages from caller-supplied package names without user confirmation. In downstream consumers that pass attacker-controlled project configuration into this path, this can result in arbitrary package installation and code execution during CLI bootstrap.
The vulnerable method is installLocalGenerators(), which calls repository.install() directly without prompting the user.
Patches
Upgrade to yeoman-environment 6.0.1, which adds an interactive confirmation prompt before installation (PR #753).
Workarounds
None.
Resources
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42089 has been found in yeoman-environment.
Successful exploitation can lead to full system takeover. CVSS score: 8.6/10.
What to do: upgrade yeoman-environment to 6.0.1 or later.
If unsure, ask your IT team or search "yeoman-environment CVE-2026-42089" on the vendor's site.
CVE-2026-42089 (yeoman-environment) — CWE-829 / CVSS v3 8.6
Attack vector: local / unauthenticated
Patched: 6.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-829) exists in yeoman-environment.
Check the vendor advisory for the affected versions of yeoman-environment.
Severity: High (CVSS 8.6/10). Successful exploitation can lead to full system takeover.
Update to 6.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'yeoman-environment' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'yeoman-environment' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
yeoman-environmentを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade yeoman-environment to 6.0.1ステージング環境で 6.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com