← Back
CVE-2026-55157
OS Command Injection in @ooples/token-optimizer-mcp (CVE-2026-55157)
Summary
OS command injection in @ooples/token-optimizer-mcp (CVE-2026-55157). Risk of unauthorized operations or information disclosure. Exploitable via ``smart_user``. Mitigation: upgrade to `5.1.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-55157** has been found in @ooples/token-optimizer-mcp.
Attackers can target a specific entry point like ``smart_user`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade @ooples/token-optimizer-mcp to **5.1.0** or later.
If unsure, ask your IT team or search "@ooples/token-optimizer-mcp CVE-2026-55157" on the vendor's site.
CVE-2026-55157 (@ooples/token-optimizer-mcp) — CWE-78 /
Attack surface: `smart_user` / `username` / `getent` / `grep`
Patched: `5.1.0` — 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 @ooples/token-optimizer-mcp. Attackers reach the vulnerable code path via ``smart_user`` without authentication.
📍 Affected scope
@ooples/token-optimizer-mcp — . Attack surface: `smart_user` / `username` / `getent` / `grep`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.1.0**.
🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r '@ooples/token-optimizer-mcp' .` 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 '@ooples/token-optimizer-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@ooples/token-optimizer-mcp` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @ooples/token-optimizer-mcp to 5.1.0ステージング環境で 5.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@ooples/token-optimizer-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.0"}]}]
References
- web https://github.com/ooples/token-optimizer-mcp/security/advisories/GHSA-49mq-fc6q-3h46
- web https://github.com/ooples/token-optimizer-mcp/commit/b4ee96dac799cbfba0a9f9c17844ce9d613cbcc7
- web https://github.com/ooples/token-optimizer-mcp/releases/tag/v5.1.0
- web https://github.com/advisories/GHSA-49mq-fc6q-3h46