# CVE-2026-0826: Poly Voice – Possible Remote Control of Certain Poly Devices

> A buffer overflow in Poly Voice devices allows remote code execution when Interactive Connectivity Establishment is enabled.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-7v6x-2q5v-c59f

## What is CVE-2026-0826?

CVE-2026-0826 is a critical memory corruption vulnerability in HP Inc. poly_trio_8300, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In certain scenarios when the admin has enabled Interactive Connectivity Establishment (ICE), a buffer overflow could enable
               remote code execution on Poly Voice products on the Linux platform.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-0826 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0826 exists.

Public exploit code:

- HP Poly Voice Unauthenticated Remote Code Execution (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0826 is a critical memory corruption vulnerability in HP Inc. poly_trio_8300, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0826 exists.

Affected product: HP Inc. poly_trio_8300. 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-0826/ (Markdown: https://insights.sbomify.com/CVE-2026-0826/index.md)
```

## Sources

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

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