← Back
CVE-2026-55158
OS Command Injection in wktk/conflibot (CVE-2026-55158)
Summary
OS command injection in wktk/conflibot (CVE-2026-55158). Risk of unauthorized operations or information disclosure. Exploitable via ``git``. Mitigation: upgrade to `1.2.1` or later.
AI summary snake-internal / snake-material-v2
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.
Risk of unauthorized operations or information disclosure. CVSS score: ?/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 /
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
wktk/conflibot — . Attack surface: `git` / `head.ref` / `pull_request_target` / `GITHUB_TOKEN`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wktk/conflibot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wktk/conflibot` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There is no configuration-only workaround for affected versions.パッチが適用されるまでの応急処置として、There is no configuration-only workaround for affected versions. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade wktk/conflibot to 1.2.1ステージング環境で 1.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
actions
wktk/conflibot
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.1"}]}]
References
- web https://github.com/wktk/conflibot/security/advisories/GHSA-2qvg-qr73-mqxp
- web https://github.com/wktk/conflibot/commit/0107ac6
- web https://github.com/wktk/conflibot/commit/59e255c
- web https://github.com/wktk/conflibot/releases/tag/v1.2.1
- web https://github.com/wktk/conflibot/releases/tag/v2.0.0
- web https://github.com/advisories/GHSA-2qvg-qr73-mqxp