Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@argos-ci/core

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 7.5npmAmendedPublished

    @argos-ci/core: CI Branch Name OS Command Injection

    CVE-2026-59960 · GHSA-4x45-gxvp-6283

    Affected
    • npm @argos-ci/core <= 6.2.0
    Fixed in
    6.2.1· Vendor fix available
    Issue
    CI Branch Name OS Command Injection in @argos-ci/core Summary @argos-ci/core@6.2.0 passes attacker-controlled CI branch/ref strings directly into an execSync() template literal in packages/core/src/ci-environment/git.ts:89. When a CI project has hasRemoteContentAccess: false, the Argos upload flow calls getMergeBaseCommitSha(), which invokes gitFetch() with the unsanitized branch name. Because execSync() passes the command string to /bin/sh -c, shell metacharacters such as $() command substitution are evaluated before git runs, enabling an attacker who can influence the branch name (e.g., via a pull request) to execute arbitrary OS commands on the CI runner. CVSS Base Score: 7.5 (High). Details The vulnerable sink is in packages/core/src/ci-environment/git.ts:87-90: execSync() with a template-literal string invokes /bin/sh -c "<command". The shell expands $(), backticks, ;, and other metacharacters before spawning git, so any special characters present in input.ref or input.target…

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

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