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