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

published 2026-09-10 59 d ago modified 2026-09-30 39 d ago also GHSA-4x45-gxvp-6283 , EUVD-2026-77641

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits: 0; none known

Argos JavaScript provides official Argos SDKs for JavaScript. Prior to Argos core package version 6.2.1, attacker-controlled CI branch or ref values from GITHUB_HEAD_REF or ARGOS_BRANCH can flow through config.branch and getMergeBaseCommitSha() when hasRemoteContentAccess is false. The gitFetch() and gitMergeBase() functions in packages/core/src/ci-environment/git.ts interpolate these values into execSync() command strings executed by /bin/sh -c, so shell metacharacters in a pull-request branch name can execute arbitrary commands with the Argos upload process privileges on the CI runner. Successful exploitation can expose CI secrets, alter build artifacts, or compromise the runner. This issue is fixed in Argos core package version 6.2.1.

Patch / fix

fixed in 1 links 3

npm @argos-ci/core 6.2.1

github.com/argos-ci/argos-javascript@8355f3a commit
github.com/argos-ci/argos-javascript#319 pull request
github.com/argos-ci/argos-javascript/releases/tag/@argos-ci/core@6.2.1 release

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 55 d ago (2026-09-14)

Exploit prediction

0.64% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	@argos-ci/core	<6.2.1	6.2.1

Affected products

argos-ci argos-javascript

Classification

Weakness

CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary