Skip to main content
VulnerabilityPublished Updated

CVE-2025-57601: Use of Hard-coded Credentials

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate this vulnerability, European organizations using AiKaan Cloud Controller should immediately: 1) Request or enforce the implementation of unique, per-device SSH keys instead of a single hardcoded key to eliminate the single point of failure. 2) Implement robust key management practices, including secure generation, storage, and rotation of SSH keys. 3) Employ network segmentation and strict access controls to limit exposure of the remote access server and administrative interfaces. 4) Monitor network traffic for anomalous reverse SSH tunnel activity and unauthorized connections. 5) Use multi-factor authentication (MFA) for administrator accounts to reduce the risk of credential compromise. 6) If possible, disable or restrict the 'Open Remote Terminal' feature until a secure authentication model is in place. 7) Engage with AiKaan for patches or updates addressing this vulnerability and apply them promptly once available. 8) Conduct regular security audits and penetration testing focused on IoT/edge device management infrastructure to detect similar weaknesses. These steps go beyond generic advice by focusing on key management, network controls, and operational monitoring tailored to the specific design flaw.

Description

AiKaan Cloud Controller uses a single hardcoded SSH private key and the username `proxyuser` for remote terminal access to all managed IoT/edge devices. When an administrator initiates "Open Remote Terminal" from the AiKaan dashboard, the controller sends this same static private key to the target device. The device then uses it to establish a reverse SSH tunnel to a remote access server, enabling browser-based SSH access for the administrator. Because the same `proxyuser` account and SSH key are reused across all customer environments: - An attacker who obtains the key (e.g., by intercepting it in transit, extracting it from the remote access server, or from a compromised admin account) can impersonate any managed device. - They can establish unauthorized reverse SSH tunnels and interact with devices without the owner's consent. This is a design flaw in the authentication model: compromise of a single key compromises the trust boundary between the controller and devices.

References

Community reviews

Loading reviews…