# CVE-2025-68717: Auth bypass in n/a

> Attackers can bypass authentication on KAYSUS routers to access sensitive configuration data and execute privileged actions by exploiting session validation flaws.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-4cc6-4h77-4425

## What is CVE-2025-68717?

CVE-2025-68717 is a critical authentication bypass vulnerability in n/a, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KAYSUS KS-WR3600 routers with firmware 1.0.5.9.1 allow authentication bypass during session validation. If any user is logged in, endpoints such as /cgi-bin/system-tool accept unauthenticated requests with empty or invalid session values. This design flaw lets attackers piggyback on another user's active session to retrieve sensitive configuration data or execute privileged actions without authentication.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Kaysus Ks-Wr3600 Firmware.

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

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

## Is CVE-2025-68717 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-68719](https://insights.sbomify.com/CVE-2025-68719/): Information disclosure in n/a (high 8.8)
- [CVE-2025-68716](https://insights.sbomify.com/CVE-2025-68716/): Hardcoded credentials in n/a (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68717 is a critical authentication bypass vulnerability in n/a, published on 8 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-68717 in the wild and no public exploit code.

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

## Sources

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

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