PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-92629 Lenovo CVE debrief

A potential improper authorization vulnerability was reported in Lenovo Baiying PC Client, distributed exclusively in the Chinese market, that could allow a local authenticated user to execute arbitrary code with elevated privileges. This vulnerability affects Lenovo Baiying PC Client deployments, particularly in Chinese markets. Defenders should assess exposure and prioritize verification and remediation efforts to prevent potential exploitation and limit damage. The vulnerability is reported to be exploitable by a local authenticated user, who could potentially execute arbitrary code with elevated privileges.

Vendor
Lenovo
Product
Baiying PC Client
CVSS
HIGH 7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-15
Original CVE updated
2026-10-16
Advisory published
2026-10-15
Advisory updated
2026-10-16

Who should care

Defenders responsible for Lenovo Baiying PC Client deployments, particularly in Chinese markets, should assess exposure and prioritize verification and remediation efforts.

Why it matters

Defenders should prioritize verifying Lenovo Baiying PC Client versions and assessing local authenticated user privileges to prevent potential exploitation and limit damage.

  • Verify and update Lenovo Baiying PC Client versions to prevent potential exploitation
  • Assess local authenticated user privileges to limit potential damage

Technical summary

The vulnerability is reported in Lenovo Baiying PC Client, distributed exclusively in the Chinese market. A local authenticated user could potentially exploit this vulnerability to execute arbitrary code with elevated privileges. The vulnerability affects Lenovo Baiying PC Client versions, and defenders should prioritize verifying the presence of Lenovo Baiying PC Client version 1.1.0.295 or earlier and assessing local authenticated user privileges. The technical details of the vulnerability are not explicitly stated, but it is reported to be an improper

Defensive priority

Defenders should prioritize verifying the presence of Lenovo Baiying PC Client version 1.1.0.295 or earlier and assessing local authenticated user privileges.

Recommended defensive actions

  • Verify Lenovo Baiying PC Client version and assess local authenticated user privileges
  • Review and update Lenovo Baiying PC Client to version 1.1.0.295 or later if necessary
  • Monitor system logs for potential exploitation attempts

Evidence notes

The CVE record and source item provide details on the potential improper authorization vulnerability in Lenovo Baiying PC Client. The vulnerability is reported to be exploitable by a local authenticated user, who could potentially execute arbitrary code with elevated privileges. The source item provides additional information on the vulnerability, including its potential impact and affected scope. However, the exact scope of affected systems and potential impact are not explicitly The

Sources and references

Verified primary and authoritative sources

  • CVE-2026-92629 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-92629

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-92629 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92629

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • CVE-2026-92629

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/92xxx/CVE-2026-92629.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://iknow.lenovo.com.cn/detail/442628

    Supplemental source - vendor-advisory

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.