# CVE-2025-7072: Hardcoded credentials in KAON CG3000T/CG3000CT routers

> Unauthenticated remote attackers can use hardcoded root credentials to execute commands on KAON CG3000T/CG3000TC routers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2026
- **Updated:** 9 Jan 2026
- **Also known as:** GHSA-c223-65f8-3p5p

## What is CVE-2025-7072?

CVE-2025-7072 is a critical vulnerability in KAON CG3000T, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The firmware in KAON CG3000TC and CG3000T routers contains hard-coded credentials in clear text (shared across all routers of this model) that an unauthenticated remote attacker could use to execute commands with root privileges.
This vulnerability has been fixed in firmware version: 1.00.67 for CG3000TC and 1.00.27 for CG3000T.

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

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


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

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

## Is CVE-2025-7072 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7072 is a critical vulnerability in KAON CG3000T, published on 9 Jan 2026. 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-7072 in the wild and no public exploit code.

Affected product: KAON CG3000T. 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-7072/ (Markdown: https://insights.sbomify.com/CVE-2025-7072/index.md)
```

## Sources

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

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