PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-62650 Siemens CVE debrief

A vulnerability in Reyrolle 7SR5 (All versions < V2.70) allows an authenticated, low-privileged remote attacker to escalate privileges to an administrative level by bypassing role-based access control (RBAC) restrictions through manipulation of request data. This vulnerability could allow for unauthorized administrative access, potentially leading to further exploitation and lateral movement within affected systems. Defenders should assess exposure and prioritize remediation for systems with versions prior to V2.70.

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 systems, particularly those with versions prior to V2.70, should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure that affected systems are identified and remediated to prevent potential exploitation.

Why it matters

CVE-2026-62650 allows an authenticated, low-privileged remote attacker to escalate privileges to an administrative level, potentially leading to further exploitation and lateral movement.

  • Privilege escalation to administrative level
  • Bypass of role-based access control (RBAC) restrictions
  • Potential for lateral movement and further exploitation

Technical summary

Server-side authorization checks in the web-based management interface of Reyrolle 7SR5 (All versions < V2.70) are not properly enforced, allowing role-based access control (RBAC) restrictions to be bypassed through manipulation of request data. This vulnerability could allow an authenticated, low-privileged remote attacker to escalate privileges to an administrative level, potentially leading to further exploitation and lateral movement. Defenders should prioritize verifying and applying the vendor's remediation for Reyrolle 7SR5 versions prior to V2.70.

Defensive priority

Defenders should prioritize verifying and applying the vendor's remediation for Reyrolle 7SR5 versions prior to V2.70, and restrict access to the web-based management interface.

Recommended defensive actions

  • Verify and apply the vendor's remediation for Reyrolle 7SR5 versions prior to V2.70
  • Restrict access to the web-based management interface
  • Monitor for suspicious activity on the affected system
  • 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 and apply the vendor's remediation for Reyrolle 7SR5 versions prior to V2.70. The lack of detailed information on affected versions and specific remediation steps may hinder thorough vulnerability management.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-62650 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-62650 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.