# CVE-2026-16754: Weak cryptography in Smart Camera C33

> Improper certificate validation in Lenovo Smart Cameras allows adjacent attackers to intercept or manipulate network communications.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-3hh9-228g-qmjp

## What is CVE-2026-16754?

CVE-2026-16754 is a medium-severity vulnerability in Lenovo Smart Camera C33, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A potential improper certificate validation vulnerability was reported in Lenovo Smart Camera C33, distributed exclusively in the Chinese market, that could allow an adjacent user to intercept or manipulate network communications.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-16754?


## How do I fix CVE-2026-16754?

No fix has been published for CVE-2026-16754 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16754 being exploited?

There is no known exploitation of CVE-2026-16754 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16754 and fix it if it is affected.

What it is: CVE-2026-16754 is a medium-severity vulnerability in Lenovo Smart Camera C33, published on 15 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-16754 in the wild and no public exploit code.

Affected product: Lenovo Smart Camera C33. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16754/ (Markdown: https://insights.sbomify.com/CVE-2026-16754/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16754
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16754
- OSV: https://osv.dev/vulnerability/CVE-2026-16754

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16754/
Summaries are generated and may contain mistakes; the official description above is the record.