Skip to content
major vulnerability· requires attention

Affects Reyrolle 7SR5 protective relays used in power/utility infrastructure; unauthenticated remote DoS against critical grid devices can disrupt operations and public services.

IoT

CVE-2026-62648

8.7
High
EPSS 0.33%Patch availableSep 8, 2026

Unauthenticated HTTP URL length flaw in Reyrolle 7SR5 allows remote crash/reboot (DoS).

common questions

Is CVE-2026-62648 being exploited?

Not confirmed. CVE-2026-62648 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-62648?

CVE-2026-62648 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-62648?

Yes. A fix has been recorded for CVE-2026-62648. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-62648 affect?

CVE-2026-62648 affects Siemens Reyrolle 7SR5 (< V2.70), Reyrolle 7SR5 relay protection devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62648?

Upgrade to V2.70 ASAP; block/ACL HTTP to devices and segment networks.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Siemens Reyrolle 7SR5 (< V2.70)Reyrolle 7SR5 relay protection devices
impact

Unauthenticated remote attacker can trigger out-of-bounds write via crafted HTTP URL, crashing/rebooting the relay and causing denial of service to protection systems.

action required

Immediate action required

affected versions
Siemens Reyrolle 7SR5
  • affected< V2.70

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free