# CVE-2026-62653: Memory corruption in Reyrolle 7SR5

> An unauthenticated attacker with physical access can trigger memory corruption in firmware update mode, potentially causing crashes or arbitrary code execution.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-wp7r-98f8-j5f3

## What is CVE-2026-62653?

CVE-2026-62653 is a high-severity memory corruption vulnerability in Siemens Reyrolle 7SR5, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in Reyrolle 7SR5 (All versions < V2.70). The input received over a proprietary communication protocol that is exposed when the device is placed into a special firmware-update mode is not properly validated, resulting in a memory corruption condition. This could allow an unauthenticated attacker with physical access to the device to cause a crash and potentially execute arbitrary code on the device.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-62653?


## How do I fix CVE-2026-62653?

No fix has been published for CVE-2026-62653 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62653 being exploited?

There is no known exploitation of CVE-2026-62653 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62653 and fix it if it is affected.

What it is: CVE-2026-62653 is a high-severity memory corruption vulnerability in Siemens Reyrolle 7SR5, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62653 in the wild and no public exploit code.

Affected product: Siemens Reyrolle 7SR5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62653/ (Markdown: https://insights.sbomify.com/CVE-2026-62653/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62653
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62653
- OSV: https://osv.dev/vulnerability/CVE-2026-62653

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62653/
Summaries are generated and may contain mistakes; the official description above is the record.