CVE-2026-62646

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.4EG
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.4Exploit: 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 session identifier is generated using an algorithm with insufficient randomness, resulting in a token with low entropy that can be predicted or brute-forced within a feasible number of attempts. This could allow an unauthenticated remote attacker to derive valid session identifiers and bypass authentication.

CVSS v3
7.4
EG Score
7.4(high)
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
Severity74% × 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 10, 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-62646(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 25× in last 7d / 47× 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 06:50 UTCGHSA enrichment
  2. 2026-09-18 19:32 UTCEG score recompute
  3. 2026-09-18 19:32 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 08:16 UTCGHSA enrichment
  6. 2026-09-17 21:00 UTCEG score recompute
  7. 2026-09-17 21:00 UTCGHSA enrichment
  8. 2026-09-17 09:44 UTCGHSA enrichment
  9. 2026-09-16 22:27 UTCEG score recompute
  10. 2026-09-16 22:27 UTCGHSA enrichment
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 10:47 UTCEG score recompute
  13. 2026-09-16 10:47 UTCGHSA enrichment
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 23:31 UTCGHSA enrichment
  16. 2026-09-15 12:15 UTCEG score recompute
  17. 2026-09-15 12:14 UTCGHSA enrichment
  18. 2026-09-15 00:57 UTCGHSA enrichment
  19. 2026-09-14 13:41 UTCGHSA enrichment
  20. 2026-09-14 02:17 UTCEG score recompute
  21. 2026-09-14 02:17 UTCGHSA enrichment
  22. 2026-09-13 15:01 UTCGHSA enrichment
  23. 2026-09-13 03:44 UTCGHSA enrichment
  24. 2026-09-12 16:26 UTCEG score recompute
  25. 2026-09-12 16:26 UTCGHSA enrichment
Show 22 more
  1. 2026-09-12 05:10 UTCGHSA enrichment
  2. 2026-09-11 17:53 UTCEG score recompute
  3. 2026-09-11 17:53 UTCGHSA enrichment
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-11 06:37 UTCGHSA enrichment
  7. 2026-09-10 19:21 UTCEG score recompute
  8. 2026-09-10 19:21 UTCGHSA enrichment
  9. 2026-09-10 18:26 UTCEG score recompute
  10. 2026-09-10 18:26 UTCGHSA enrichment
  11. 2026-09-10 16:57 UTCEG score recompute
  12. 2026-09-10 16:57 UTCGHSA enrichment
  13. 2026-09-10 05:41 UTCGHSA enrichment
  14. 2026-09-09 18:24 UTCGHSA enrichment
  15. 2026-09-09 07:06 UTCEG score recompute
  16. 2026-09-09 07:06 UTCGHSA enrichment
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-08 19:50 UTCGHSA enrichment
  19. 2026-09-08 09:41 UTCEG score recompute
  20. 2026-09-08 09:41 UTCGHSA enrichment
  21. 2026-09-08 08:36 UTCEG score recompute
  22. 2026-09-08 08:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62646?
CVE-2026-62646 is a high vulnerability published on September 8, 2026. A vulnerability has been identified in Reyrolle 7SR5 (All versions < V2.70). A session identifier is generated using an algorithm with insufficient randomness, resulting in a token with low entropy that can be predicted or brute-forced within a feasible number of attempts. This could allow an…
When was CVE-2026-62646 disclosed?
CVE-2026-62646 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62646 actively exploited?
CVE-2026-62646 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 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-62646?
CVE-2026-62646 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-62646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62646, 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-62646

Explore →

Is Your Infrastructure Affected by CVE-2026-62646?

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

Start Free Scan →Browse All CVEs