PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-62648 Siemens CVE debrief

A vulnerability in Reyrolle 7SR5 (All versions < V2.70) allows an unauthenticated remote attacker to cause a denial-of-service condition by crashing the device, resulting in a reboot. The vulnerability is caused by improper validation of the URL component in pre-authenticated HTTP messages, leading to an out-of-bounds write condition in memory. Defenders should assess exposure and potential impact of denial-of-service condition. The CVE record and NVD entry provide details on the vulnerability.

Vendor
Siemens
Product
Reyrolle 7SR5
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-08
Original CVE updated
2026-09-08
Advisory published
2026-09-08
Advisory updated
2026-09-08

Who should care

Defenders responsible for Reyrolle 7SR5 devices should assess exposure and potential impact of denial-of-service condition. Defenders should prioritize verifying exposure of Reyrolle 7SR5 devices and assessing the potential impact of a denial-of-service condition. Operators, administrators, and security teams managing Reyrolle 7SR5 devices should review the vulnerability and take necessary actions to mitigate the risk.

Why it matters

Defenders should prioritize verifying exposure of Reyrolle 7SR5 devices and assessing potential impact of denial-of-service condition due to limited information on affected versions and remediation.

  • Denial-of-service condition resulting in device reboot
  • Potential disruption to critical infrastructure operations

Technical summary

The length of the URL component in pre-authenticated HTTP messages is not properly validated, resulting in an out-of-bounds write condition in memory, allowing an unauthenticated remote attacker to crash the device. This could allow an unauthenticated remote attacker to cause a denial-of-service condition. The vulnerability affects Reyrolle 7SR5 devices with versions less than V2.70. Defenders should prioritize verifying exposure of Reyrolle 7SR5 devices and assessing the potential impact of a denial-of-service condition.

Defensive priority

Defenders should prioritize verifying exposure of Reyrolle 7SR5 devices and assessing the potential impact of a denial-of-service condition.

Recommended defensive actions

  • Verify exposure of Reyrolle 7SR5 devices
  • Assess potential impact of denial-of-service condition
  • Monitor device logs for suspicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but additional information on affected versions and remediation is limited. Defenders should verify exposure of Reyrolle 7SR5 devices and assess potential impact of denial-of-service condition due to limited information on affected versions and remediation. The source detail is limited, and explicit evidence-limit language and defensive verification tasks are required.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-62648 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-62648

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-62648 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-62648

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.