What is CVE-2026-75940?

CVE-2026-75940 is A vulnerability was reported in Lenovo Health Android Application, distributed exclusively in the Chinese market, that could allow an…. The supplied enrichment data classifies it as Credentials mapped to CWE-798 Use of Hard-coded Credentials.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-75940. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-75940 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-75940 using CVSS 9.1, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalCredentialspublic exploit

CVE-2026-75940

CVE-2026-75940 — A vulnerability was reported in Lenovo Health Android Application, distributed exclusively in the Chinese market, that could allow an…

A vulnerability was reported in Lenovo Health Android Application, distributed exclusively in the Chinese market, that could allow an attacker to access sensitive health-related information.

Published Sep 10, 2026Updated Sep 10, 2026Sources: NVD, Lenovo (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Lenovo

Health Application

CVSS base

9.1

critical · 2 sources

Remediation

The vendor's own words where we have them.

Update Lenovo Health Android Application version to 1.5.0 or later.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Lenovo	Health Application	0 to <= 1.5.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.1	CVSS 3.1	critical	3.9	5.2	NVD, Lenovo (CNA), GHSA
9.3	CVSS 4.0	critical	—	—	Lenovo (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-798 · Use of Hard-coded Credentials

Bypass Protection Mechanism
Read Application Data
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands

Mitigation: For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7]. In Windows environments, the Encrypted File System (EFS) may provide some protection.

Weakness & attack patterns

CWE-798Use of Hard-coded Credentials

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-70 · Try Common or Default Usernames and PasswordsCAPEC-191 · Read Sensitive Constants Within an Executable

T1552.001Unsecured Credentials: Credentials in files
T1078.001Valid Accounts: Default Accounts

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Health Application.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.1 (AV:N)
Sep 10, 2026 · NVD
Initial · CVE published
Sep 10, 2026 · NVD
Added · GHSA-w7vv-xhmp-9qcq published (critical)
Sep 10, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 10, 2026 · SOCRadar CTI

References

3 on the record

iknow.lenovo.com.cn/detail/442248
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-75940
NVD
github.com/advisories/GHSA-w7vv-xhmp-9qcq
Exploit, Third Party Advisory

Elsewhere on this site

Lenovoevery CVE for this vendor
Credentialssame class
CWE-798other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-75940 is A vulnerability was reported in Lenovo Health Android Application, distributed exclusively in the Chinese market, that could allow an…, a critical vulnerability affecting Health Application from Lenovo. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-75940. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.