Vulnerabilities in pkg:npm/@conventional-changelog/git-client

PACKAGE
Advisory Identifier: GHSA-vh25-5764-9wcr
Advisory Summary

CVE-2025-59433 is a MODERATE (CVSS 5.3) @conventional-changelog/git-client has argument injection vulnerability vulnerability (CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')) affecting @conventional changelog/git client libraries in the npm ecosystem. The issue involves @conventional-changelog/git-client has argument injection vulnerability. Remediation is available by upgrading affected packages to version 2.0.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@conventional-changelog/git-client

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@conventional-changelog/git-client. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-vh25-5764-9wcr CVE-2025-59433 MODERATE @conventional-changelog/git-client has Argument Injection vulnerability

CVE-2025-59433 at a Glance

CVE Identifier CVE-2025-59433
GHSA Identifier GHSA-vh25-5764-9wcr
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Affected Product @conventional changelog/git client
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:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:H).

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

How to Fix CVE-2025-59433

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

@conventional-changelog/git-client fixed: 2.0.0
npm install @conventional-changelog/git-client@2.0.0
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 @conventional-changelog/git-client

How to Check if You Are Affected

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

npm ls @conventional-changelog/git-client

Analyze the terminal output to locate any version of @conventional changelog/git client in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.0), your application is affected.

Note: The npm ls @conventional-changelog/git-client 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-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection'), where the product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. In @conventional changelog/git client, 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

## Background on exploitation This vulnerability manifests with the library's `getTags()` API, which allows specifying extra parameters passed to the `git log` command. In another API by this library - `getRawCommits()` there are secure practices taken to ensure that the extra parameter `path` is unable to inject an argument by ending the `git log` command with the special shell syntax `--`. However, the library does not follow the same practice for `getTags()` not attempts to sanitize for user input, validate the given params, or restrcit them to an allow list. Nor does it properly pass command-line flags to the `git` binary using the double-dash POSIX characters (`--`) to communicate the end of options. Thus, allowing users to exploit an argument injection vulnerability in Git due to the `--output=` command-line option that results with overwriting arbitrary files. ## Exploit 1. Install `@conventional-changelog/git-client@1.0.1` or earlier 2. Prepare a Git directory to be used as source 3. Create the following script for the proof-of-concept: ```js import { GitClient, } from "@conventional-changelog/git-client"; async function main() { const gitDirectory = "/tmp/some-git-directory"; const client = new GitClient(gitDirectory); const params = ["--output=/tmp/r2d2"]; for await (const tag of client.getTags(params)) { console.log(tag); } } main(); ``` 3. Observe new file created on disk at `/tmp/r2d2` ## Impact While the scope is only limited to writing a file with input from the git log result, it still allows to specify and overwrite any arbitrary files on disk, such as `.env` or as far as critical system configuration at `/etc` if the application is running as privileged `root` user. It may be the library's design choice to expose a generic `params` object to allow any consuming users to specify random Git command line arguments, however it could be abused by attackers when developers aren't aware of the security risks which aren't communicated. As such, I recommend not ignoring, and either patching this insecure design gap with hardened secure coding practices (like in other APIs mentioned previously) or adding a security disclaimer to this library's documentation. # Author / Credit Liran Tal

CVE-2025-59433 Affected @conventional changelog/git client Versions

1 component(s)
Fixed Versions:
2.0.0
Product / Package Ecosystem Affected Versions Fixed Version
@conventional-changelog/git-client
npm
< 2.0.0
2.0.0

References

Frequently Asked Questions

What is CVE-2025-59433?
CVE-2025-59433 is a security vulnerability in @conventional changelog/git client involving @conventional-changelog/git-client has Argument Injection vulnerability under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection').
Which @conventional changelog/git client versions are affected?
Affected versions include releases prior to 2.0.0 across affected packages: @conventional-changelog/git-client.
What version fixes CVE-2025-59433?
Upgrading to 2.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @conventional-changelog/git-client affected?
Yes, @conventional-changelog/git-client is affected in releases prior to 2.0.0. Upgrade your dependency to 2.0.0 or later.
What is the CVSS score of CVE-2025-59433?
CVE-2025-59433 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:H.
What CWE is associated with CVE-2025-59433?
CVE-2025-59433 is classified under CWE-88: Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') (The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.).
How can I check npm dependencies for CVE-2025-59433?
Run the dependency tree command: 'npm ls @conventional-changelog/git-client'. 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-vh25-5764-9wcr",
  "modified" : "2025-09-22T21:59:10Z",
  "published" : "2025-09-22T18:01:01Z",
  "aliases" : [ "CVE-2025-59433" ],
  "summary" : "@conventional-changelog/git-client has Argument Injection vulnerability",
  "details" : "## Background on exploitation\n\nThis vulnerability manifests with the library's `getTags()` API,\nwhich allows specifying extra parameters passed to the `git log` command. In another API by this library - `getRawCommits()` there are secure practices taken to ensure that the extra parameter `path` is unable to inject an argument by ending the `git log` command with the special shell syntax `--`.\nHowever, the library does not follow the same practice for `getTags()` not attempts to sanitize for user input, validate the given params, or restrcit them to an allow list. Nor does it properly pass command-line flags to the `git` binary using the double-dash POSIX characters (`--`) to communicate the end of options.\n\nThus, allowing users to exploit an argument injection vulnerability in Git due to the\n`--output=` command-line option that results with overwriting arbitrary files.\n\n## Exploit\n\n1. Install `@conventional-changelog/git-client@1.0.1` or earlier\n2. Prepare a Git directory to be used as source\n3. Create the following script for the proof-of-concept:\n\n```js\nimport {\n  GitClient,\n} from \"@conventional-changelog/git-client\";\n\nasync function main() {\n  const gitDirectory = \"/tmp/some-git-directory\";\n  const client = new GitClient(gitDirectory);\n\n  const params = [\"--output=/tmp/r2d2\"];\n  for await (const tag of client.getTags(params)) {\n    console.log(tag);\n  }\n}\n\nmain();\n```\n\n3. Observe new file created on disk at `/tmp/r2d2`\n\n## Impact\n\nWhile the scope is only limited to writing a file with input from the git log result, it still allows to specify and overwrite any arbitrary files on disk, such as `.env` or as far as critical system configuration at `/etc` if the application is running as privileged `root` user.\n\nIt may be the library's design choice to expose a generic `params` object to allow any consuming users to specify random Git command line arguments, however it could be abused by attackers when developers aren't aware of the security risks which aren't communicated. As such, I recommend not ignoring, and either patching this insecure design gap with hardened secure coding practices (like in other APIs mentioned previously) or adding a security disclaimer to this library's documentation.\n\n# Author / Credit\n\nLiran Tal",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@conventional-changelog/git-client"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/conventional-changelog/conventional-changelog/security/advisories/GHSA-vh25-5764-9wcr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-59433"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/conventional-changelog/conventional-changelog/commit/d95c9ffac05af58228bd89fa0ba37ad65741c6a2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/conventional-changelog/conventional-changelog"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-88" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-22T18:01:01Z",
    "nvd_published_at" : "2025-09-22T20:15:38Z"
  }
}