CVE-2026-9127

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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
Trending — 3 sources updated this week
7.3EG
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.3Exploit: None knownExposed: 0

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

A remote code execution security issue exists within Studio 5000 Logix Designer® due to incorrect authorization on a configuration file. This can allow any authenticated user to modify the paths of external tools configured within the application. If exploited, an attacker could alter the configuration to point to a malicious executable, resulting in arbitrary code execution when any user interacts with the external tools functionality.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (1)

Auto-updated Jul 14, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-9127(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 33× 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-07-30 16:28 UTCEPSS rescore
  2. 2026-07-30 13:18 UTCEG score recompute
  3. 2026-07-30 13:18 UTCGHSA enrichment
  4. 2026-07-30 01:08 UTCGHSA enrichment
  5. 2026-07-29 12:55 UTCGHSA enrichment
  6. 2026-07-29 00:45 UTCEG score recompute
  7. 2026-07-29 00:45 UTCGHSA enrichment
  8. 2026-07-28 15:37 UTCEPSS rescore
  9. 2026-07-28 12:36 UTCGHSA enrichment
  10. 2026-07-28 00:25 UTCGHSA enrichment
  11. 2026-07-27 12:05 UTCGHSA enrichment
  12. 2026-07-26 23:56 UTCGHSA enrichment
  13. 2026-07-26 11:47 UTCEG score recompute
  14. 2026-07-26 11:46 UTCGHSA enrichment
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-24 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:23 UTCEG score recompute
  19. 2026-07-22 14:08 UTCEPSS rescore
  20. 2026-07-21 15:25 UTCEPSS rescore
  21. 2026-07-21 15:25 UTCEPSS rescore
  22. 2026-07-20 17:08 UTCEPSS rescore
  23. 2026-07-19 14:31 UTCEPSS rescore
  24. 2026-07-18 10:04 UTCEPSS rescore
  25. 2026-07-17 04:30 UTCGHSA enrichment
Show 8 more
  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-16 16:21 UTCGHSA enrichment
  3. 2026-07-16 04:10 UTCGHSA enrichment
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 16:00 UTCGHSA enrichment
  6. 2026-07-15 03:50 UTCGHSA enrichment
  7. 2026-07-14 15:41 UTCEG score recompute
  8. 2026-07-14 15:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-9127?
CVE-2026-9127 is a high vulnerability published on July 14, 2026. A remote code execution security issue exists within Studio 5000 Logix Designer® due to incorrect authorization on a configuration file. This can allow any authenticated user to modify the paths of external tools configured within the application. If exploited, an attacker could alter the…
When was CVE-2026-9127 disclosed?
CVE-2026-9127 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9127 actively exploited?
CVE-2026-9127 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 98.5% of all scored CVEs.
What is the CVSS score of CVE-2026-9127?
CVE-2026-9127 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-9127?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9127, 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

Explore the affected products and dependency analysis for CVE-2026-9127

Explore →

Is Your Infrastructure Affected by CVE-2026-9127?

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