CVE-2025-41702: Welotec EG400Mk2-D11001-000101 · Use of Hard-coded Cryptographic Key
Affects Welotec EG400Mk2-D11001-000101Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Welotec EG400Mk2-D11001-000101 | Affected
| Fixed in– |
AI-suggested
Given the absence of official patches, European organizations should immediately implement compensating controls. First, restrict network access to the affected devices by placing them behind firewalls or VPNs, limiting exposure to trusted internal networks only. Employ network segmentation to isolate these devices from critical systems and sensitive data. Monitor network traffic for anomalous JWT token generation or unusual authentication attempts. If possible, disable or restrict the egOS WebGUI backend access until a patch is available. Organizations should also consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block unauthorized JWT tokens or suspicious API calls. Regularly audit device configurations and logs for signs of compromise. Engage with Welotec support channels to obtain updates or workarounds. Finally, plan for timely patch deployment once available and consider alternative devices if the risk cannot be adequately mitigated.
Description
The JWT secret key is embedded in the egOS WebGUI backend and is readable to the default user. An unauthenticated remote attacker can generate valid HS256 tokens and bypass authentication/authorization due to the use of hard-coded cryptographic key.