Command Injection in danger (CVE-2026-16629)
Summary
Command injection in danger (CVE-2026-16629). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 13.0.8 or later.
Original description
The description as published by the source.
A vulnerability was identified in danger danger-js up to 13.0.7. Impacted is the function danger.git.diffForFile of the file source/platforms/git/localGetFileAtSHA.ts of the component CLI. Such manipulation of the argument File leads to os command injection. The attack needs to be performed locally. Upgrading to version 13.0.8 is recommended to address this issue. The name of the patch is 087a7290264cc6fb7154ea8c2552a7b2cb8b33a3. It is advisable to upgrade the affected component.
Source: NIST National Vulnerability Database 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-16629 has been found in danger.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade danger to 13.0.8 or later.
If unsure, ask your IT team or search "danger CVE-2026-16629" on the vendor's site.
CVE-2026-16629 (danger) — CWE-77 / CVSS v3 5.3
Attack vector: local / no user interaction
Patched: 13.0.8 — 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-77) exists in danger.
Check the vendor advisory for the affected versions of danger.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 13.0.8.
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 'danger' . 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 'danger' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dangerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade danger to 13.0.8ステージング環境で 13.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com
- report vuldb.com
- web github.com
- web github.com