CVE-2026-55673

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

PowSyBl (Power System Blocks) is a framework to build power system oriented software. Prior to 7.2.2, UnixLocalCommandExecutor and WindowsLocalCommandExecutor concatenate command arguments and environment variables into strings interpreted through bash -c or cmd /c without sufficient escaping. Attacker-controlled values reaching UnixLocalCommandExecutor.execute, WindowsLocalCommandExecutor.execute, LocalComputationManager.execute, ParallelLoadFlowActionSimulator.run, ActionSimulatorTool.run, AmplModelRunner.run, or AmplModelRunner.runAsync can break out of the intended command and execute arbitrary shell commands as the JVM user. The affected itools paths include action-simulator with task-count, security-analysis with external, and dynamic-security-analysis. Downstream CLI tools, libraries, REST front ends, and multi-tenant grid-analysis services that forward less-trusted contingency identifiers or computation parameters into these APIs can expose the injection remotely. This issue is fixed in version 7.2.2.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

August 28, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Aug 28, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Command Injection in LocalCommandExecutor-s · Advisory · powsybl/powsybl-core · GitHub

https://github.com/powsybl/powsybl-core/security/advisories/GHSA-jqvf-j3ww-r8c7
github_release Patch Available

v7.2.2

Patch available: powsybl/powsybl-core v7.2.2

https://github.com/powsybl/powsybl-core/releases/tag/v7.2.2
github_pr

Apply fix for GHSA-jqvf-j3ww-r8c7

Fix merged in powsybl/powsybl-core PR #3973 on 2026-06-24 — awaiting tagged release

https://github.com/powsybl/powsybl-core/pull/3973
github_commit

commit 7aa28d8c2492 (powsybl/powsybl-core)

Fix landed in powsybl/powsybl-core commit 7aa28d8c2492 — awaiting tagged release

https://github.com/powsybl/powsybl-core/commit/7aa28d8c2492bbcd061585cb498acce72d5ed79a
github_commit Patch Available

commit 17461264d1d1 (powsybl/powsybl-core)

Patch available: powsybl/powsybl-core v7.2.2 (contains commit 17461264d1d1)

https://github.com/powsybl/powsybl-core/commit/17461264d1d18f9bba43bb7855f251e9fa55a4db

Vendor Advisories for CVE-2026-55673(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.powsybl:powsybl-computation-local1.0.0 ... 7.2.1 (124 versions)7.2.2—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 42× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 21:28 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 20:50 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 18:58 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 06:56 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 07:17 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-13 19:49 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-12 20:10 UTCEG score recompute
  14. 2026-09-11 20:30 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 20:52 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 00:27 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 18:50 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-06 19:09 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-05 19:29 UTCEG score recompute
  25. 2026-09-04 19:51 UTCEG score recompute
Show 17 more
  1. 2026-09-04 07:55 UTCEG score recompute
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 20:23 UTCEG score recompute
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 19:17 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 07:22 UTCEG score recompute
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-31 19:31 UTCEG score recompute
  10. 2026-08-31 18:57 UTCEG score recompute
  11. 2026-08-30 19:46 UTCEG score recompute
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 07:55 UTCEG score recompute
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 20:24 UTCEG score recompute▲ 7.10
  16. 2026-08-28 20:24 UTCNVD updateCVSS v3 → 7.1 · CVSS v4 → 7.1
  17. 2026-08-28 19:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55673?
CVE-2026-55673 is a high vulnerability published on August 28, 2026. PowSyBl (Power System Blocks) is a framework to build power system oriented software. Prior to 7.2.2, UnixLocalCommandExecutor and WindowsLocalCommandExecutor concatenate command arguments and environment variables into strings interpreted through bash -c or cmd /c without sufficient escaping.…
When was CVE-2026-55673 disclosed?
CVE-2026-55673 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55673 actively exploited?
CVE-2026-55673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.5% of all scored CVEs.
What is the CVSS score of CVE-2026-55673?
CVE-2026-55673 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-55673?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55673, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55673

Explore →

Is Your Infrastructure Affected by CVE-2026-55673?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs