Authentication bypass via hard-coded JWT signing key
Published Oct 17, 2025 · Updated Oct 17, 2025
Authentication bypass in Moxa network security appliances and routers allows remote attackers to gain administrative access. A hard-coded secret key signs authentication JSON Web Tokens, so attackers can mint valid tokens that impersonate any user. No credentials or user interaction are required; a forged token grants device-level data access, configuration control, and service interruption, without reported confidentiality or integrity impact on subsequent systems.
Summary
What happened
Authentication bypass in Moxa network security appliances and routers allows remote attackers to gain administrative access. A hard-coded secret key signs authentication JSON Web Tokens, so attackers can mint valid tokens that impersonate any user. No credentials or user interaction are required; a forged token grants device-level data access, configuration control, and service interruption, without reported confidentiality or integrity impact on subsequent systems.
The record
- CVE
- CVE-2025-6950
- Published
- Oct 17, 2025
- Updated
- Oct 17, 2025
- Vendor
- Moxa
- Product
- EDF-G1002-BP Series
- Classifications
- CWE-798, CAPEC-37, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 17, 2025CVE publishedPublication date reported by the CVE source.
- Oct 17, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0 <=3.17
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