Vulnerabilities in pkg:npm/danger

PACKAGE
Advisory Identifier: GHSA-3x93-p86w-5jvh
Advisory Summary

CVE-2026-16629 is a MODERATE (CVSS 5.3) danger allows local os command vulnerability (CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')) affecting Danger libraries in the npm ecosystem. The issue involves danger allows local os command injection through crafted file paths. Remediation is available by upgrading affected packages to version 13.0.8.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/danger

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/danger. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-3x93-p86w-5jvh CVE-2026-16629 MODERATE danger allows local OS command injection through crafted file paths

CVE-2026-16629 at a Glance

CVE Identifier CVE-2026-16629
GHSA Identifier GHSA-3x93-p86w-5jvh
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Affected Product Danger
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2026-16629

To remediate this vulnerability, upgrade all affected Danger dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

danger fixed: 13.0.8
npm install danger@13.0.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls danger

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-16629, inspect your project dependencies using npm:

npm ls danger

Analyze the terminal output to locate any version of Danger in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 13.0.8), your application is affected.

Note: The npm ls danger command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), where the product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. In Danger, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2026-16629 Affected Danger Versions

1 component(s)
Fixed Versions:
13.0.8
Product / Package Ecosystem Affected Versions Fixed Version
danger
npm
< 13.0.8
13.0.8

References

Frequently Asked Questions

What is CVE-2026-16629?
CVE-2026-16629 is a security vulnerability in Danger involving danger allows local OS command injection through crafted file paths under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection').
Which Danger versions are affected?
Affected versions include releases prior to 13.0.8 across affected packages: danger.
What version fixes CVE-2026-16629?
Upgrading to 13.0.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is danger affected?
Yes, danger is affected in releases prior to 13.0.8. Upgrade your dependency to 13.0.8 or later.
What is the CVSS score of CVE-2026-16629?
CVE-2026-16629 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L.
What CWE is associated with CVE-2026-16629?
CVE-2026-16629 is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') (The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.).
How can I check npm dependencies for CVE-2026-16629?
Run the dependency tree command: 'npm ls danger'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-3x93-p86w-5jvh",
  "modified" : "2026-09-04T20:51:19Z",
  "published" : "2026-07-23T00:31:28Z",
  "aliases" : [ "CVE-2026-16629" ],
  "summary" : "danger allows local OS command injection through crafted file paths",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "danger"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "13.0.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-16629"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/danger/danger-js/pull/1513"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/danger/danger-js/commit/087a7290264cc6fb7154ea8c2552a7b2cb8b33a3"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/danger/danger-js"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/danger/danger-js/releases/tag/13.0.8"
  }, {
    "type" : "WEB",
    "url" : "https://vuldb.com/cve/CVE-2026-16629"
  }, {
    "type" : "WEB",
    "url" : "https://vuldb.com/submit/860211"
  }, {
    "type" : "WEB",
    "url" : "https://vuldb.com/vuln/382377"
  }, {
    "type" : "WEB",
    "url" : "https://vuldb.com/vuln/382377/cti"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-77" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-04T20:51:19Z",
    "nvd_published_at" : "2026-07-22T22:16:29Z"
  }
}