← Back
CVE-2026-42290 high CVSS 7.8

OS Command Injection in protobufjs-cli (CVE-2026-42290)

Summary

OS command injection in protobufjs-cli (CVE-2026-42290). Successful exploitation can lead to full system takeover. Exploitable via ``pbts``. Mitigation: upgrade to `2.0.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-42290** has been found in protobufjs-cli. Attackers can target a specific entry point like ``pbts`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 7.8/10. What to do: upgrade protobufjs-cli to **2.0.2** or later. If unsure, ask your IT team or search "protobufjs-cli CVE-2026-42290" on the vendor's site.
CVE-2026-42290 (protobufjs-cli) — CWE-78 / CVSS v3 7.8 Attack vector: local / unauthenticated Attack surface: `pbts` / `child_process.exec` Patched: `2.0.2` — apply immediately Workaround: Do not run affected versions of `pbts` on attacker-controlled file names or paths. 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 protobufjs-cli. Attackers reach the vulnerable code path via ``pbts`` without authentication.
📍 Affected scope
protobufjs-cli — . Attack surface: `pbts` / `child_process.exec`.
🔥 Severity
Severity: High (CVSS 7.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.0.2**.
🛡️ Workaround
Workaround: Do not run affected versions of `pbts` on attacker-controlled file names or paths.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'protobufjs-cli' .` 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

  1. 1
    Identify exposure identify
    grep -r 'protobufjs-cli' . | grep -v node_modules

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

  2. 5
    Apply temporary workaround mitigate
    Do not run affected versions of `pbts` on attacker-controlled file names or paths.

    パッチが適用されるまでの応急処置として、Do not run affected versions of `pbts` on attacker-controlled file names or paths. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade protobufjs-cli to 2.0.2

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

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

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

Affected packages

npm protobufjs-cli
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.0.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →