# CVE-2025-57602: Hardcoded credentials in n/a

> Remote attackers can use a hardcoded SSH key to access the AiKaan IoT cloud controller, enabling shell access and pivoting to connected devices.

- **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:** 22 Sep 2025
- **Updated:** 23 Sep 2025
- **Also known as:** GHSA-m3jm-xvp6-99vj

## What is CVE-2025-57602?

CVE-2025-57602 is a critical vulnerability in n/a, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient hardening of the proxyuser account in the AiKaan IoT management platform, combined with the use of a shared, hardcoded SSH private key, allows remote attackers to authenticate to the cloud controller, gain interactive shell access, and pivot into other connected IoT devices. This can lead to remote code execution, information disclosure, and privilege escalation across customer environments.

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

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


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

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

## Is CVE-2025-57602 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57602 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57602 is a critical vulnerability in n/a, published on 22 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57602 exists.

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-57602/ (Markdown: https://insights.sbomify.com/CVE-2025-57602/index.md)
```

## Sources

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

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