{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-35905 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-35905 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35905 is a critical vulnerability in n/a, published on 4 Jun 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-2026-35905 and fix it if it is affected.\n\nWhat it is: CVE-2026-35905 is a critical vulnerability in n/a, published on 4 Jun 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-2026-35905 in the wild and no public exploit code.\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-2026-35905/ (Markdown: https://insights.sbomify.com/CVE-2026-35905/index.md)","id":"CVE-2026-35905","markdown":"https://insights.sbomify.com/CVE-2026-35905/index.md","name":"CVE-2026-35905","record":{"aliases":["GHSA-chq3-rh33-9xqp"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"T3 Technology CPE","requires_auth":"none","summary":"Attackers can gain root access to T3 Technology CPE devices using hardcoded superadmin credentials, compromising network security.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"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-259","name":"Use of Hard-coded Password"}],"description":"T3 Technology CPE models T625Pro v1.0.07, T6825G v1.0.03, and T7281 v1.0.03 were discovered to contain a hardcoded password for root access under the \"superadmin\" account.","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":"Hardcoded credentials in n/a","id":"CVE-2026-35905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2026-35906"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2026-35904"},"products":["n/a"],"published":"2026-06-04","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-06-08","vendors":["n/a"]},"summary":"Attackers can gain root access to T3 Technology CPE devices using hardcoded superadmin credentials, compromising network security.","url":"https://insights.sbomify.com/CVE-2026-35905/"}