Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-59960 high CVSS 7.5

OS Command Injection in @argos-ci/core (CVE-2026-59960)

Summary

OS command injection in @argos-ci/core (CVE-2026-59960). Successful exploitation can lead to full system takeover. Exploitable via GET /v2/project. Mitigation: upgrade to 6.2.1 or later.

Original description

The description as published by the source.

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:

function gitFetch(input: { ref: string; depth: number; target: string }) {
  execSync(
    `git fetch --force --update-head-ok --depth ${input.depth} origin ${input.ref}:${input.target}`,
  );
}

execSync() with a template-literal string invokes /bin/sh -c "". The shell expands $(), backticks, ;, and other metacharacters before spawning git, so any special characters present in input.ref or input.target are interpreted as shell instructions.

A secondary sink exists at packages/core/src/ci-environment/git.ts:67:

execSync(`git merge-base ${input.head} ${input.base}`)

Complete data flow (source → sink):

  1. `packages/core/src/ci-environm…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-59960 has been found in @argos-ci/core.
Attackers can target a specific entry point like GET /v2/project over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade @argos-ci/core to 6.2.1 or later.
If unsure, ask your IT team or search "@argos-ci/core CVE-2026-59960" on the vendor's site.

CVE-2026-59960 (@argos-ci/core) — CWE-78 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /v2/project / GET /v2/project / POST /v2/builds / POST /builds.
Patched: 6.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

OS command injection (CWE-78) exists in @argos-ci/core. Attackers reach the vulnerable code path via GET /v2/project.

📍 Affected scope

Check the vendor advisory for the affected versions of @argos-ci/core. Attack surface: GET /v2/project / GET /v2/project / POST /v2/builds / POST /builds..

🔥 Severity

Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 6.2.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /v2/project requests with malformed payloads or SQL meta-characters. Run grep -r '@argos-ci/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@argos-ci/core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @argos-ci/core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /v2/project' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /v2/project への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade @argos-ci/core to 6.2.1

    ステージング環境で 6.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /v2/project on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @argos-ci/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.2.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details