Skip to content

← Public intelligence

npm package

git-commiters

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.7npmAmendedPublished

    git-comiters Command Injection vulnerability

    CVE-2025-59831 · GHSA-g38c-wxjf-xrh6

    Affected
    • npm git-commiters < 0.1.2
    Fixed in
    0.1.2· Vendor fix available
    Issue
    Background on the vulnerability This vulnerability manifests with the library's primary exported API: gitCommiters(options, callback) which allows specifying options such as cwd for current working directory and revisionRange as a revision pointer, such as HEAD. However, the library does not sanitize for user input or practice secure process execution API to separate commands from their arguments and as such, uncontrolled user input is concatenated into command execution. Exploit 1. Install git-commiters@0.1.1 or earlier 2. Initiaizlie a new Git directory with commits in it 3. Create the following script in that directory: 3. Observe new file created on disk at /tmp/pwn The git commiters functionality works as expected, too, despite the command execution, which further hinders the problem as it may not be apparent that a command injection occured on a running application. Credit Liran Tal

    Recommended action: Upgrade to 0.1.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →