Vulnerabilities in pkg:maven/com.powsybl/powsybl-computation-local
PACKAGECVE-2026-55673 is a HIGH powsybl core has command injection vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Powsybl computation local libraries in the Maven ecosystem. The issue involves powsybl core has command injection in localcommandexecutor-s. Remediation is available by upgrading affected packages to version 7.2.2.
pkg:maven/com.powsybl/powsybl-computation-local
Vulnerability advisories affecting package pkg:maven/com.powsybl/powsybl-computation-local. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-jqvf-j3ww-r8c7 | CVE-2026-55673 | HIGH | PowSyBl Core has Command Injection in LocalCommandExecutor-s |
CVE-2026-55673 at a Glance
How to Fix CVE-2026-55673
To remediate this vulnerability, upgrade all affected Powsybl computation local dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>com.powsybl</groupId>
<artifactId>powsybl-computation-local</artifactId>
<version>7.2.2</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=com.powsybl
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-55673, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=com.powsybl
Analyze the terminal output to locate any version of Powsybl computation local in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.2.2), your application is affected.
Note: The mvn dependency:tree -Dincludes=com.powsybl command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Powsybl computation local, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-55673 Affected Powsybl computation local Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
com.powsybl:powsybl-computation-local
|
Maven |
< 7.2.2
|
7.2.2
|
References
Frequently Asked Questions
What is CVE-2026-55673?
Which Powsybl computation local versions are affected?
What version fixes CVE-2026-55673?
Is powsybl-computation-local affected?
What CWE is associated with CVE-2026-55673?
How can I check Maven dependencies for CVE-2026-55673?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jqvf-j3ww-r8c7",
"modified" : "2026-08-28T18:37:28Z",
"published" : "2026-08-28T18:37:28Z",
"aliases" : [ "CVE-2026-55673" ],
"summary" : "PowSyBl Core has Command Injection in LocalCommandExecutor-s",
"details" : "### Impact\n\n#### Description\nBoth `AbstractLocalCommandExecutor` OS-dependent implementations are subject to **CWE-78** (OS Command Injection), with a secondary **CWE-88** (Argument Injection) concern via environment variables.\n\nThe 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.\n\nThe sink is reachable through public APIs that accept `List<String>` arguments without any documented indication that elements undergo shell interpretation.\n\nAny caller — CLI, library integration, or embedding service — that forwards data from a less-trusted source into these APIs inherits the vulnerability.\n\n#### Vulnerable elements\nThe vulnerable elements are:\n- Public methods:\n - `UnixLocalCommandExecutor.execute(...)`\n - `WindowsLocalCommandExecutor.execute(...)`\n - `LocalComputationManager.execute(...)`\n - `ParallelLoadFlowActionSimulator.run(...)`\n - `ActionSimulatorTool.run(...)`\n - `AmplModelRunner.run(...)`\n - `AmplModelRunner.runAsync(...)`\n- **itools** commands:\n - `action-simulator`, when the `task-count` option is defined\n - `security-analysis`, when the `external` option is defined\n - `dynamic-security-analysis`\n\n\n#### Characteristics\n\nThe vulnerability characteristics are the following:\n- It allows **arbitrary shell command execution** as the JVM user (read, write, execute any file; spawn processes; exfiltrate data; etc.)\n- There are **multiple independent injection vectors** within a single vulnerable call:\n - `args` elements (weakly escaped — bypassable via `$(...)`, backticks, escaped quotes)\n - Environment variable values (unescaped — bypassable via `;`, `\\n`, or shell metacharacters)\n- It is **silent** from the caller's perspective: the `List<String>` API gives no indication that shell interpretation occurs.\n- 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.\n\n\n#### Am I impacted?\n\nYou 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.\n\n\n### Patches\n\n`com.powsybl:powsybl-computation-local:7.2.2` and higher\n\n\n### Workarounds\n\nIf 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:\n- On Unix/Linux systems:\n - `\\`, `!`, `#`, `$`, `^`, `&`, `*`, `(`, `)`, `{`, `}`, `|`, `[`, `]`, `\\`, `;`, `\\`, `\"`, `,`, `<`, `>`, `?`, ` `\n- On Windows:\n - `%`, `!`, `\"`, `\\n`, `\\r`, `^`",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "com.powsybl:powsybl-computation-local"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "7.2.2"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 7.2.1"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/powsybl/powsybl-core/security/advisories/GHSA-jqvf-j3ww-r8c7"
}, {
"type" : "WEB",
"url" : "https://github.com/powsybl/powsybl-core/pull/3973"
}, {
"type" : "WEB",
"url" : "https://github.com/powsybl/powsybl-core/commit/17461264d1d18f9bba43bb7855f251e9fa55a4db"
}, {
"type" : "WEB",
"url" : "https://github.com/powsybl/powsybl-core/commit/7aa28d8c2492bbcd061585cb498acce72d5ed79a"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/powsybl/powsybl-core"
}, {
"type" : "WEB",
"url" : "https://github.com/powsybl/powsybl-core/releases/tag/v7.2.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-78", "CWE-88" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-28T18:37:28Z",
"nvd_published_at" : null
}
}