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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-59960: 0.64% estimated exploitation activity in the next 30 days; percentile 50.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

10 Sep 2026, 22:34 UTC

Last modified by the source

1 Oct 2026, 08:56 UTC

Source last checked

26 Oct 2026, 13:06 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4x45-gxvp-6283

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-4x45-gxvp-6283

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-4x45-gxvp-6283

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-59960

Advisory: @argos-ci/core: CI Branch Name OS Command Injection
IDs: CVE-2026-59960, GHSA-4x45-gxvp-6283
Record: https://patchnext.com/advisories/cve-2026-59960 (revision 3, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @argos-ci/core 6.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @argos-ci/core: affected <= 6.2.0; fixed in 6.2.1

## Suggested inspection (read-only)
- `npm ls @argos-ci/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @argos-ci/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4x45-gxvp-6283 (GitHub-reviewed advisory GHSA-4x45-gxvp-6283 lists affected ranges: npm @argos-ci/core >=0 <=6.2.0)
- Verified: https://osv.dev/vulnerability/GHSA-4x45-gxvp-6283 (OSV record GHSA-4x45-gxvp-6283 lists affected ranges: npm @argos-ci/core >=0 <6.2.1 (fixed))

Commands are suggestions: review each one before running it.