poly_trio_8300: Stack-based Buffer Overflow
CVE-2026-0826 is a critical-severity stack-based buffer overflow vulnerability in poly_trio_8300 from HP, with a CVSS 4.0 base score of 9.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 8.1.7 as the first without the flaw, so updating poly_trio_8300 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 32.2% chance of exploitation within 30 days, which is in the top 1.65% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update poly_trio_8300 to 8.1.7 or a later version.
- Update poly_trio_8500 to 7.2.8 or a later version.
- Update poly_trio_8800 to 7.2.8 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| HP | poly_trio_8300 | before 8.1.7 | 8.1.7 |
| HP | poly_trio_8500 | before 7.2.8 | 7.2.8 |
| HP | poly_trio_8800 | before 7.2.8 | 7.2.8 |
| HP | poly_vvx | before 6.4.8 | 6.4.8 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- PresentThe target must be in a specific state or configuration for the attack to work.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- NoneNo loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- NoneNo loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- NoneNo loss of availability on systems beyond the vulnerable one.
Vector: 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA (hp.com).
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Stack-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the stack.
How developers prevent this class of flaw
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Implement and perform bounds checking on input.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Stack-based Buffer Overflow vulnerabilities
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 8.6 High severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.