{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67305 exists.","fix":"No fix has been published for CVE-2025-67305 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67305 is a critical vulnerability in n/a, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-67305 and fix it if it is affected.\n\nWhat it is: CVE-2025-67305 is a critical vulnerability in n/a, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67305 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-67305/ (Markdown: https://insights.sbomify.com/CVE-2025-67305/index.md)","id":"CVE-2025-67305","markdown":"https://insights.sbomify.com/CVE-2025-67305/index.md","name":"CVE-2025-67305","record":{"aliases":["GHSA-mc6c-v4m2-858f"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"RUCKUS Network Director","requires_auth":"none","summary":"Hardcoded SSH keys in RUCKUS Network Director allow attackers to authenticate as postgres, access the database, and escalate privileges.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ruckus_network_director","vendor":"commscope"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"In RUCKUS Network Director (RND) \u003c 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-67305","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CVE RECORD.","id":"CVE-2025-67315"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-67304"},"products":["n/a"],"published":"2026-02-19","related":[{"cvss_score":9.9,"headline":"Command injection in SmartZone","id":"CVE-2025-44961","kev_date_added":null,"published":"2025-08-04"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-67304","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":9,"headline":"Hardcoded credentials in Network Director","id":"CVE-2025-44963","kev_date_added":null,"published":"2025-08-04"},{"cvss_score":8.8,"headline":"Hardcoded credentials in Network Director","id":"CVE-2025-44955","kev_date_added":null,"published":"2025-08-04"},{"cvss_score":8.5,"headline":"Auth bypass in SmartZone","id":"CVE-2025-44957","kev_date_added":null,"published":"2025-08-04"},{"cvss_score":8.5,"headline":"Command injection in SmartZone","id":"CVE-2025-44960","kev_date_added":null,"published":"2025-08-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["n/a"]},"summary":"Hardcoded SSH keys in RUCKUS Network Director allow attackers to authenticate as postgres, access the database, and escalate privileges.","url":"https://insights.sbomify.com/CVE-2025-67305/"}