Skip to main content
VulnerabilityPublished Updated

CVE-2025-67305: Use of Hard-coded Cryptographic Key

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% 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 19 Feb 2026

  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 CVE-2025-67305, organizations should take the following specific actions: 1) Immediately upgrade RUCKUS Network Director to version 4.5.0.56 or later once the vendor releases a patch that removes the hardcoded SSH keys. 2) Until a patch is available, restrict network access to the RND appliance by implementing strict network segmentation and firewall rules that limit SSH and management interface access to trusted administrative hosts only. 3) Conduct an audit of existing RND deployments to identify any unauthorized administrative users or suspicious activity that may indicate exploitation. 4) Rotate all credentials and keys related to the RND environment after patching to invalidate any compromised keys. 5) Monitor network traffic and logs for unusual SSH authentication attempts or database access patterns. 6) Consider deploying intrusion detection/prevention systems (IDS/IPS) to detect exploitation attempts targeting this vulnerability. 7) Educate network and security teams about the risk and ensure incident response plans include steps for handling potential RND compromises. These targeted measures go beyond generic advice by focusing on immediate containment, detection, and remediation specific to the nature of this vulnerability.

Description

In RUCKUS Network Director (RND) < 4.5.0.56, the OVA appliance contains hardcoded SSH keys for the postgres user. These keys are identical across all deployments, allowing an attacker with network access to authenticate via SSH without a password. Once authenticated, the attacker can access the PostgreSQL database with superuser privileges, create administrative users for the web interface, and potentially escalate privileges further.

References

Community reviews

Loading reviews…