TLS private-key disclosure via plaintext firmware storage
Published Sep 26, 2025 · Updated Sep 26, 2025
Private-key disclosure in Mercusys MW305R 3.30 and earlier allows physically proximate attackers to obtain the router's TLS key. The firmware image stores an RSA private key as an unencrypted pem.key file that becomes visible after unpacking nested binary data. Physical access to extract the firmware is required; the disclosed key enables protected-traffic decryption and man-in-the-middle impersonation.
Summary
What happened
Private-key disclosure in Mercusys MW305R 3.30 and earlier allows physically proximate attackers to obtain the router's TLS key. The firmware image stores an RSA private key as an unencrypted pem.key file that becomes visible after unpacking nested binary data. Physical access to extract the firmware is required; the disclosed key enables protected-traffic decryption and man-in-the-middle impersonation.
The record
- CVE
- CVE-2025-56463
- Published
- Sep 26, 2025
- Updated
- Sep 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1552.004
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2025CVE publishedPublication date reported by the CVE source.
- Sep 26, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Firmware extraction proof of conceptproof of concept · demonstrated
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