# CVE-2025-41702: egOS WebGUI Hard-Coded JWT Secret Enables Authentication Bypass

> An unauthenticated remote attacker can bypass authentication and gain unauthorized access to the egOS WebGUI by using a hard-coded JWT secret key.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-6498-6rj5-p7pf

## What is CVE-2025-41702?

CVE-2025-41702 is a critical vulnerability in Welotec EG400Mk2-D11001-000101, published on 26 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-41702?


## How do I fix CVE-2025-41702?

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

## Is CVE-2025-41702 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41702 and fix it if it is affected.

What it is: CVE-2025-41702 is a critical vulnerability in Welotec EG400Mk2-D11001-000101, published on 26 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41702 in the wild and no public exploit code.

Affected product: Welotec EG400Mk2-D11001-000101. 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-2025-41702/ (Markdown: https://insights.sbomify.com/CVE-2025-41702/index.md)
```

## Sources

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

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