{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-69425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69425 is a critical vulnerability in RUCKUS Networks vRIoT IoT Controller, published on 9 Jan 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-69425 and fix it if it is affected.\n\nWhat it is: CVE-2025-69425 is a critical vulnerability in RUCKUS Networks vRIoT IoT Controller, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-69425 in the wild and no public exploit code.\n\nAffected product: RUCKUS Networks vRIoT IoT Controller. 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-69425/ (Markdown: https://insights.sbomify.com/CVE-2025-69425/index.md)","id":"CVE-2025-69425","markdown":"https://insights.sbomify.com/CVE-2025-69425/index.md","name":"CVE-2025-69425","record":{"aliases":["GHSA-gfvg-q74f-527q"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"IoT controller firmware","requires_auth":"none","summary":"Attackers can extract hardcoded TOTP secrets and static tokens to execute arbitrary OS commands with root privileges on Ruckus vRIoT IoT Controllers.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) expose a command execution service on TCP port 2004 running with root privileges. Authentication to this service relies on a hardcoded Time-based One-Time Password (TOTP) secret and an embedded static token. An attacker who extracts these credentials from the appliance or a compromised device can generate valid authentication tokens and execute arbitrary OS commands with root privileges, resulting in complete system compromise.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Ruckus vRIoT IoT Controller \u003c 3.0.0.0 Hardcoded Tokens RCE","id":"CVE-2025-69425","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":"Ruckus vRIoT IoT Controller \u003c 3.0.0.0 Hardcoded SSH Credentials RCE","id":"CVE-2025-69426"},"packages":[],"prev":{"headline":"NULL Pointer Dereference in PKCS12_item_decrypt_d2i_ex function","id":"CVE-2025-69421"},"products":["vRIoT IoT Controller"],"published":"2026-01-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["RUCKUS Networks"]},"summary":"Attackers can extract hardcoded TOTP secrets and static tokens to execute arbitrary OS commands with root privileges on Ruckus vRIoT IoT Controllers.","url":"https://insights.sbomify.com/CVE-2025-69425/"}