{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1408 exists.","fix":"No fix has been published for CVE-2026-1408 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1408 is a low-severity vulnerability in Beetel 777VR1, published on 25 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-1408 and fix it if it is affected.\n\nWhat it is: CVE-2026-1408 is a low-severity vulnerability in Beetel 777VR1, published on 25 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1408 exists.\n\nAffected product: Beetel 777VR1. 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-1408/ (Markdown: https://insights.sbomify.com/CVE-2026-1408/index.md)","id":"CVE-2026-1408","markdown":"https://insights.sbomify.com/CVE-2026-1408/index.md","name":"CVE-2026-1408","record":{"aliases":["GHSA-rgjg-mj5f-rchp"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Beetel 777VR1","requires_auth":"none","summary":"Attackers with physical access can exploit weak UART password requirements to bypass authentication on Beetel 777VR1 devices.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"777vr1_firmware","vendor":"beetel"}],"cvss":{"score":1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"description":"A weakness has been identified in Beetel 777VR1 up to 01.00.09/01.00.09_55. This vulnerability affects unknown code of the component UART Interface. Executing a manipulation can lead to weak password requirements. The physical device can be targeted for the attack. The attack requires a high level of complexity. It is stated that the exploitability is difficult. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.","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":"Beetel 777VR1 UART weak password","id":"CVE-2026-1408","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Beetel 777VR1 UART excessive authentication","id":"CVE-2026-1409"},"packages":[],"prev":{"headline":"Beetel 777VR1 UART information disclosure","id":"CVE-2026-1407"},"products":["777VR1"],"published":"2026-01-25","related":[{"cvss_score":8.7,"headline":"Beetel 777VR1 Web Management hard-coded credentials","id":"CVE-2026-2616","kev_date_added":null,"published":"2026-02-17"},{"cvss_score":6.3,"headline":"Beetel 777VR1 SSH Service risky encryption","id":"CVE-2026-2618","kev_date_added":null,"published":"2026-02-17"},{"cvss_score":5.4,"headline":"Beetel 777VR1 UART missing authentication","id":"CVE-2026-1410","kev_date_added":null,"published":"2026-01-26"},{"cvss_score":5.4,"headline":"Beetel 777VR1 UART access control","id":"CVE-2026-1411","kev_date_added":null,"published":"2026-01-26"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2020-36056","kev_date_added":null,"published":"2022-01-31"},{"cvss_score":5.3,"headline":"Beetel 777VR1 Telnet Service/SSH Service insecure default initialization of resource","id":"CVE-2026-2617","kev_date_added":null,"published":"2026-02-17"},{"cvss_score":4.8,"headline":"Cross-site scripting in n/a","id":"CVE-2020-25498","kev_date_added":null,"published":"2021-01-06"}],"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":["Beetel"]},"summary":"Attackers with physical access can exploit weak UART password requirements to bypass authentication on Beetel 777VR1 devices.","url":"https://insights.sbomify.com/CVE-2026-1408/"}