CVE-2026-62650

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.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). Server-side authorization checks in the web-based management interface are not properly enforced, allowing role-based access control (RBAC) restrictions to be bypassed through manipulation of request data. This could allow an authenticated, low-privileged remote attacker to escalate privileges to an administrative level.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
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-62650(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 22× in last 7d / 46× 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 14:24 UTCGHSA enrichment
  2. 2026-09-19 01:34 UTCEG score recompute
  3. 2026-09-19 01:34 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 12:45 UTCGHSA enrichment
  6. 2026-09-17 23:56 UTCEG score recompute
  7. 2026-09-17 23:56 UTCGHSA enrichment
  8. 2026-09-17 10:48 UTCGHSA enrichment
  9. 2026-09-16 21:56 UTCEG score recompute
  10. 2026-09-16 21:56 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 09:07 UTCEG score recompute
  13. 2026-09-16 09:07 UTCGHSA enrichment
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 20:18 UTCGHSA enrichment
  16. 2026-09-15 07:28 UTCEG score recompute
  17. 2026-09-15 07:28 UTCGHSA enrichment
  18. 2026-09-14 18:39 UTCGHSA enrichment
  19. 2026-09-14 05:50 UTCGHSA enrichment
  20. 2026-09-13 17:01 UTCEG score recompute
  21. 2026-09-13 17:01 UTCGHSA enrichment
  22. 2026-09-13 04:12 UTCGHSA enrichment
  23. 2026-09-12 15:22 UTCEG score recompute
  24. 2026-09-12 15:22 UTCGHSA enrichment
  25. 2026-09-12 02:32 UTCEG score recompute
Show 21 more
  1. 2026-09-12 02:32 UTCGHSA enrichment
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 13:42 UTCEG score recompute
  4. 2026-09-11 13:42 UTCGHSA enrichment
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-11 00:53 UTCGHSA enrichment
  7. 2026-09-10 12:03 UTCEG score recompute
  8. 2026-09-10 12:03 UTCGHSA enrichment
  9. 2026-09-09 23:13 UTCGHSA enrichment
  10. 2026-09-09 08:40 UTCEG score recompute
  11. 2026-09-09 08:40 UTCGHSA enrichment
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-08 19:50 UTCGHSA enrichment
  14. 2026-09-08 13:38 UTCEG score recompute
  15. 2026-09-08 13:38 UTCGHSA enrichment
  16. 2026-09-08 12:46 UTCEG score recompute
  17. 2026-09-08 12:45 UTCGHSA enrichment
  18. 2026-09-08 09:41 UTCEG score recompute
  19. 2026-09-08 09:41 UTCGHSA enrichment
  20. 2026-09-08 08:36 UTCEG score recompute
  21. 2026-09-08 08:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62650?
CVE-2026-62650 is a high vulnerability published on September 8, 2026. A vulnerability has been identified in Reyrolle 7SR5 (All versions < V2.70). Server-side authorization checks in the web-based management interface are not properly enforced, allowing role-based access control (RBAC) restrictions to be bypassed through manipulation of request data. This could allow…
When was CVE-2026-62650 disclosed?
CVE-2026-62650 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-62650 actively exploited?
CVE-2026-62650 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 74.9% of all scored CVEs.
What is the CVSS score of CVE-2026-62650?
CVE-2026-62650 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-62650?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62650, 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-62650

Explore →

Is Your Infrastructure Affected by CVE-2026-62650?

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

Start Free Scan →Browse All CVEs