Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55158 critical CVSS 9.1

OS Command Injection in wktk/conflibot (CVE-2026-55158)

Summary

OS command injection in wktk/conflibot (CVE-2026-55158). Confidential information can be exposed externally. Exploitable via git. Mitigation: upgrade to 1.2.1 or later.

Original description

The description as published by the source.

Impact

Versions of conflibot before 1.2.1 build git commands by string interpolation and run them through a shell. Several of the interpolated values are pull request branch names (head.ref), which are attacker-controlled: anyone can open a pull request (including from a fork) whose head branch name contains shell metacharacters such as `, $( ), ;, |, or &.

The recommended workflow runs conflibot on the pull_request_target event, where the job has access to the base repository's secrets and a write-scoped GITHUB_TOKEN. As a result, a crafted branch name causes arbitrary command execution on the runner with that write token in the environment, allowing an attacker to exfiltrate secrets and the token, push to the repository, or otherwise abuse the token's permissions. No special privileges and no maintainer interaction are required — the action runs automatically when the pull request is opened.

Affected configurations

Any workflow using wktk/conflibot at a version earlier than 1.2.1. The risk is highest under pull_request_target (the documented configuration), because that is where the write token and secrets are exposed to attacker-influenced refs.

Patches

Fixed in 1.2.1 and 2.0.0. All git invocations now use argument arrays via execFile/spawn instead of a shell, so branch names can no longer be interpreted as shell syntax, and pull requests are referenced by number through refs/pull//head rather than by branch name.…

Source: GitHub Security Advisories (Global) 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-55158 has been found in wktk/conflibot.
Attackers can target a specific entry point like git over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: upgrade wktk/conflibot to 1.2.1 or later.
If unsure, ask your IT team or search "wktk/conflibot CVE-2026-55158" on the vendor's site.

CVE-2026-55158 (wktk/conflibot) — CWE-78 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: git / head.ref / pull_request_target / GITHUB_TOKEN
Patched: 1.2.1 — apply immediately
Workaround: There is no configuration-only workaround for affected versions.
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 wktk/conflibot. Attackers reach the vulnerable code path via git without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of wktk/conflibot. Attack surface: git / head.ref / pull_request_target / GITHUB_TOKEN.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.2.1.

🛡️ Workaround

Workaround: There is no configuration-only workaround for affected versions.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wktk/conflibot' . 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 'wktk/conflibot' . | grep -v node_modules

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

  2. 2
    Apply temporary workaround mitigate 
    There is no configuration-only workaround for affected versions.

    パッチが適用されるまでの応急処置として、There is no configuration-only workaround for affected versions. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade wktk/conflibot to 1.2.1

    ステージング環境で 1.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

actions wktk/conflibot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.1"}]}]
GitHub Actions wktk/conflibot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.1"}]}]

References

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