CVE-2026-62654

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. a secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

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

A vulnerability has been identified in Reyrolle 7SR5 (All versions < V2.70). A special maintenance mode can be activated via a physical key sequence during device boot, in which the device downloads and executes program code from a network server without verifying its authenticity or integrity. This could allow an attacker with physical access to the device to upload and execute arbitrary, unsigned code.

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

Published

September 8, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic

SSA-142885

https://cert-portal.siemens.com/productcert/html/ssa-142885.html

Vendor Advisories for CVE-2026-62654(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 / 34× 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-19 10:44 UTCGHSA enrichment
  2. 2026-09-18 11:19 UTCEG score recompute
  3. 2026-09-18 11:19 UTCGHSA enrichment
  4. 2026-09-17 12:12 UTCEG score recompute
  5. 2026-09-17 12:12 UTCGHSA enrichment
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 13:02 UTCEG score recompute
  8. 2026-09-16 13:02 UTCGHSA enrichment
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 13:55 UTCEG score recompute
  11. 2026-09-15 13:55 UTCGHSA enrichment
  12. 2026-09-14 14:47 UTCEG score recompute
  13. 2026-09-14 14:47 UTCGHSA enrichment
  14. 2026-09-13 15:40 UTCGHSA enrichment
  15. 2026-09-12 16:32 UTCEG score recompute
  16. 2026-09-12 16:32 UTCGHSA enrichment
  17. 2026-09-11 17:25 UTCEG score recompute
  18. 2026-09-11 17:25 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-10 18:05 UTCEG score recompute
  22. 2026-09-10 18:05 UTCGHSA enrichment
  23. 2026-09-09 18:58 UTCEG score recompute
  24. 2026-09-09 18:58 UTCGHSA enrichment
  25. 2026-09-08 22:01 UTCEPSS rescore
Show 9 more
  1. 2026-09-08 19:50 UTCGHSA enrichment
  2. 2026-09-08 13:38 UTCEG score recompute
  3. 2026-09-08 13:38 UTCGHSA enrichment
  4. 2026-09-08 12:45 UTCEG score recompute
  5. 2026-09-08 12:45 UTCGHSA enrichment
  6. 2026-09-08 09:40 UTCEG score recompute
  7. 2026-09-08 09:39 UTCGHSA enrichment
  8. 2026-09-08 08:36 UTCEG score recompute
  9. 2026-09-08 08:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62654?
CVE-2026-62654 is a medium vulnerability published on September 8, 2026. A vulnerability has been identified in Reyrolle 7SR5 (All versions < V2.70). A special maintenance mode can be activated via a physical key sequence during device boot, in which the device downloads and executes program code from a network server without verifying its authenticity or integrity.…
When was CVE-2026-62654 disclosed?
CVE-2026-62654 was first published in the National Vulnerability Database on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62654 actively exploited?
CVE-2026-62654 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-62654?
CVE-2026-62654 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-62654?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62654, 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-62654

Explore →

Is Your Infrastructure Affected by CVE-2026-62654?

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

Start Free Scan →Browse All CVEs