{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-1716 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-1716 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1716 is a medium-severity vulnerability in Lenovo Baiying, published on 11 Mar 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-1716 and fix it if it is affected.\n\nWhat it is: CVE-2026-1716 is a medium-severity vulnerability in Lenovo Baiying, published on 11 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-1716 in the wild and no public exploit code.\n\nAffected product: Lenovo Baiying. 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-1716/ (Markdown: https://insights.sbomify.com/CVE-2026-1716/index.md)","id":"CVE-2026-1716","markdown":"https://insights.sbomify.com/CVE-2026-1716/index.md","name":"CVE-2026-1716","record":{"aliases":["GHSA-hp66-fgrj-w7fr"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lenovo Vantage","requires_auth":"low_privilege","summary":"A local authenticated user can delete arbitrary registry keys with elevated privileges in Lenovo Vantage and Baiying due to input validation flaws.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"lenovo","cpe":[{"product":"vantage","vendor":"lenovo"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"An input validation vulnerability was reported in the DeviceSettingsSystemAddin used in Lenovo Vantage and Lenovo Baiying that could allow a local authenticated user to delete arbitrary registry keys with elevated privileges.","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":"Other in Baiying","id":"CVE-2026-1716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in Baiying","id":"CVE-2026-1717"},"packages":[],"prev":{"headline":"Privilege escalation in Baiying","id":"CVE-2026-1715"},"products":["Baiying","Vantage"],"published":"2026-03-11","related":[{"cvss_score":7.8,"headline":"Privilege escalation in Vantage","id":"CVE-2023-6043","kev_date_added":null,"published":"2024-01-19"},{"cvss_score":7.3,"headline":"Privilege escalation in Vantage","id":"CVE-2020-8327","kev_date_added":null,"published":"2020-04-14"},{"cvss_score":6.9,"headline":"Privilege escalation in Baiying","id":"CVE-2026-1715","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":6.8,"headline":"Privilege escalation in Baiying","id":"CVE-2026-1717","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":6.3,"headline":"Privilege escalation in Vantage","id":"CVE-2023-6044","kev_date_added":null,"published":"2024-01-19"},{"cvss_score":4.4,"headline":"Information disclosure in Vantage","id":"CVE-2020-8316","kev_date_added":null,"published":"2020-04-14"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["Lenovo"]},"summary":"A local authenticated user can delete arbitrary registry keys with elevated privileges in Lenovo Vantage and Baiying due to input validation flaws.","url":"https://insights.sbomify.com/CVE-2026-1716/"}