# CVE-2026-32683: Information disclosure in EZVIZ APP

> Attackers can eavesdrop on network requests to obtain data due to legacy API interfaces in EZVIZ products.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-5xjc-rg5p-8xgc

## What is CVE-2026-32683?

CVE-2026-32683 is a medium-severity vulnerability in EZVIZ APP, published on 9 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Some EZVIZ products utilize older versions of cloud feature modules with legacy API interfaces, which pose a data transmission risk. Attackers can exploit this by eavesdropping on network requests to obtain data.Users are advised to upgrade the app to the latest version and enable the video encryption feature.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2026-32683 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32683 is a medium-severity vulnerability in EZVIZ APP, published on 9 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32683 in the wild and no public exploit code.

Affected product: EZVIZ APP. 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-32683/ (Markdown: https://insights.sbomify.com/CVE-2026-32683/index.md)
```

## Sources

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

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