CVE-2026-55673
Fix: powsybl/powsybl-core#3973CVE-2026-55673 is a OS Command Injection vulnerability in com.powsybl:powsybl-computation-local. O3 Security confirms whether CVE-2026-55673 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
PowSyBl Core has Command Injection in LocalCommandExecutor-s
Real-World Exposure
com.powsybl:powsybl-computation-localReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Description
Both AbstractLocalCommandExecutor OS-dependent implementations are subject to CWE-78 (OS Command Injection), with a secondary CWE-88 (Argument Injection) concern via environment variables.
The local command executor build command strings via concatenation and executes them (through bash -c for Unix, or cmd /c for Windows). Any string argument or environment variable value reaching this executor can break out of the intended command and execute arbitrary shell code as the JVM user.
The sink is reachable through public APIs that accept List<String> arguments without any documented indication that elements undergo shell interpretation.
Any caller — CLI, library integration, or embedding service — that forwards data from a less-trusted source into these APIs inherits the vulnerability.
Vulnerable elements
The vulnerable elements are:
- Public methods:
UnixLocalCommandExecutor.execute(...)WindowsLocalCommandExecutor.execute(...)LocalComputationManager.execute(...)ParallelLoadFlowActionSimulator.run(...)ActionSimulatorTool.run(...)AmplModelRunner.run(...)AmplModelRunner.runAsync(...)
- itools commands:
action-simulator, when thetask-countoption is definedsecurity-analysis, when theexternaloption is defineddynamic-security-analysis
Characteristics
The vulnerability characteristics are the following:
- It allows arbitrary shell command execution as the JVM user (read, write, execute any file; spawn processes; exfiltrate data; etc.)
- There are multiple independent injection vectors within a single vulnerable call:
argselements (weakly escaped — bypassable via$(...), backticks, escaped quotes)- Environment variable values (unescaped — bypassable via
;,\n, or shell metacharacters)
- It is silent from the caller's perspective: the
List<String>API gives no indication that shell interpretation occurs. - It exposes downstream projects: any service embedding
powsybl-core(REST front-ends, pypowsybl tooling, multi-tenant grid analysis platforms) that exposes contingency IDs or computation parameters to external input is exploitable without needing to touch powsybl's code directly.
Am I impacted?
You are vulnerable if you make direct calls to one of the vulnerable end-user methods or itools commands listed in the "Vulnerable elements" section, with user-provided parameters, without controlling them.
Patches
com.powsybl:powsybl-computation-local:7.2.2 and higher
Workarounds
If you cannot update your powsybl-computation-local version, you can check the content of the user-provided arguments when calling the vulnerable methods, by forbidding (if possible) the following characters:
- On Unix/Linux systems:
\,!,#,$,^,&,*,(,),{,},|,[,],\,;,\,",,,<,>,?,
- On Windows:
%,!,",\n,\r,^
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.powsybl:powsybl-computation-local | all versions | 7.2.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.powsybl:powsybl-computation-local. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.powsybl:powsybl-computation-local to 7.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-55673 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-55673 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-55673. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-55673 in your dependencies?
O3 detects CVE-2026-55673 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.