# CVE-2026-53414: Zoom Clients - Buffer Over-read

> A missing bounds check in Zoom Clients allows a meeting participant to cause a denial of service on another participant via network access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-q9vw-2jgv-5p57

## What is CVE-2026-53414?

CVE-2026-53414 is a medium-severity memory corruption vulnerability in Zoom Clients, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Missing bounds check in the annotator function of Zoom Clients allows buffer over-read, which may allow a meeting participant to conduct a denial of service on another participant via network access.

Weakness: CWE-126 (Buffer Over-read)

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


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

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

## Is CVE-2026-53414 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53414 is a medium-severity memory corruption vulnerability in Zoom Clients, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-53414 in the wild and no public exploit code.

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

## Sources

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

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