Firmware information disclosure via retained debugging symbols
Published Sep 8, 2026 · Updated Sep 10, 2026
Information disclosure in Siemens Reyrolle 7SR5 before 2.70 allows remote attackers to obtain firmware debugging metadata. Released firmware binaries retain debugging symbols instead of removing them, exposing structural information that simplifies firmware analysis. No device access or authentication is required because the firmware files are public; the bounded consequence is easier reverse engineering and discovery of additional flaws.
Summary
What happened
Information disclosure in Siemens Reyrolle 7SR5 before 2.70 allows remote attackers to obtain firmware debugging metadata. Released firmware binaries retain debugging symbols instead of removing them, exposing structural information that simplifies firmware analysis. No device access or authentication is required because the firmware files are public; the bounded consequence is easier reverse engineering and discovery of additional flaws.
The record
- CVE
- CVE-2026-62652
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Siemens AG
- Product
- Reyrolle 7SR5
- Classifications
- CWE-215
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <V2.70
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo