# CVE-2025-6950: Hardcoded credentials in EDF-G1002-BP Series

> An attacker can forge JWT tokens using a hard-coded key to bypass authentication and gain full administrative control over Moxa network devices.

- **Severity:** Critical 9.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-29jf-57xj-hxj2

## What is CVE-2025-6950?

CVE-2025-6950 is a critical vulnerability in Moxa EDF-G1002-BP Series, published on 17 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Use of Hard-coded Credentials vulnerability has been identified in Moxa’s network security appliances and routers. The system employs a hard-coded secret key to sign JSON Web Tokens (JWT) used for authentication. This insecure implementation allows an unauthenticated attacker to forge valid tokens, thereby bypassing authentication controls and impersonating any user. Exploitation of this vulnerability can result in complete system compromise, enabling unauthorized access, data theft, and full administrative control over the affected device. While successful exploitation can severely impact the confidentiality, integrity, and availability of the affected device itself, there is no loss of confidentiality or integrity within any subsequent systems.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-6950 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6950 is a critical vulnerability in Moxa EDF-G1002-BP Series, published on 17 Oct 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-6950 in the wild and no public exploit code.

Affected product: Moxa EDF-G1002-BP Series. 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-6950/ (Markdown: https://insights.sbomify.com/CVE-2025-6950/index.md)
```

## Sources

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

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