npm package report

Is @argos-ci/core safe?

1 known vulnerability, worst severity HIGH.

cvss
7.5

how bad it is if exploited, out of 10

epss
0.50%

chance of exploitation in the next 30 days

xyz score
4.0

CyberXYZ composite, out of 10

fig. 01 — GHSA-4x45-gxvp-6283, the advisory selected below

// advisories

GHSA-4x45-gxvp-6283

HIGHCVE-2026-59960

@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 metacha

Affected
>=0, <6.2.1, <= 6.2.0
Fixed in
6.2.1
Weakness
CWE-78
Published
2026-09-10
Source
osv

NVDMITREOSV

// dependencies

9 direct, 5 carrying known advisories, worst CRITICAL

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 02:43 UTC. The most recent advisory here was published 2026-09-10. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @argos-ci/core safe? npm package security report | CyberXYZ