CVE-2026-55673

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (47th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 advisoryMentions a patch (unverified)

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 pull request

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 rangeFix by version rangeDependents
com.powsybl:powsybl-computation-local1.0.0 ... 7.2.1 (124 versions)
  • every version up to 7.2.2: fixed in 7.2.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:16 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-10 00:49 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-09 02:37 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  13. 2026-10-08 00:50 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-06 19:16 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-05 19:26 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-05 07:26 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  21. 2026-10-03 19:18 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  23. 2026-10-02 19:27 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-02 07:37 UTCEG score recompute
Show 64 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-09-30 19:49 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-09-30 03:49 UTCEG score recompute
  5. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  6. 2026-09-29 08:57 UTCEG score recompute
  7. 2026-09-28 21:08 UTCEG score recompute
  8. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-09-27 20:06 UTCEG score recompute
  10. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  11. 2026-09-26 20:24 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-09-26 08:04 UTCEG score recompute
  14. 2026-09-24 20:23 UTCEG score recompute
  15. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-09-23 20:42 UTCEG score recompute
  17. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-22 21:04 UTCEG score recompute
  19. 2026-09-21 21:09 UTCEG score recompute
  20. 2026-09-20 21:31 UTCEG score recompute
  21. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-09-19 21:50 UTCEG score recompute
  23. 2026-09-18 21:28 UTCEG score recompute
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-09-17 20:50 UTCEG score recompute
  26. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  27. 2026-09-16 18:58 UTCEG score recompute
  28. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  29. 2026-09-16 06:56 UTCEG score recompute
  30. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  31. 2026-09-15 07:17 UTCEG score recompute
  32. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  33. 2026-09-13 19:49 UTCEG score recompute
  34. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  35. 2026-09-12 20:10 UTCEG score recompute
  36. 2026-09-11 20:30 UTCEG score recompute
  37. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  38. 2026-09-10 20:52 UTCEG score recompute
  39. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  40. 2026-09-09 00:27 UTCEG score recompute
  41. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  42. 2026-09-07 18:50 UTCEG score recompute
  43. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  44. 2026-09-06 19:09 UTCEG score recompute
  45. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  46. 2026-09-05 19:29 UTCEG score recompute
  47. 2026-09-04 19:51 UTCEG score recompute
  48. 2026-09-04 07:55 UTCEG score recompute
  49. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  50. 2026-09-02 20:23 UTCEG score recompute
  51. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  52. 2026-09-01 19:17 UTCEG score recompute
  53. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  54. 2026-09-01 07:22 UTCEG score recompute
  55. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  56. 2026-08-31 19:31 UTCEG score recompute
  57. 2026-08-31 18:57 UTCEG score recompute
  58. 2026-08-30 19:46 UTCEG score recompute
  59. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  60. 2026-08-30 07:55 UTCEG score recompute
  61. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-08-28 20:24 UTCEG score recomputeFirst assessed: 7.1 HIGH
  63. 2026-08-28 20:24 UTCNVD updateCVSS v3 → 7.1 · CVSS v4 → 7.1
  64. 2026-08-28 19:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55673?
CVE-2026-55673 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-55673 published?
The CVE record for CVE-2026-55673 was published on August 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55673 actively exploited?
CVE-2026-55673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55673?
CVE-2026-55673 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55673?
A fix for CVE-2026-55673 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55673 are linked in the Vendor Advisories panel on this page.

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.