Unauthenticated code execution via ICE buffer overflow
Published Jun 1, 2026 · Updated Jun 1, 2026
Stack-based buffer overflow in HP Poly Trio 8300 before 8.1.7 and Trio 8500 and 8800 before 7.2.8 allows remote attackers to execute code. HP identifies the affected behavior only as a buffer overflow triggered when Interactive Connectivity Establishment processing is enabled; no public source names the parser, field, or faulty operation. An administrator must enable ICE; once enabled, remote attackers need no authentication or user interaction to execute code on the phone.
Summary
What happened
Stack-based buffer overflow in HP Poly Trio 8300 before 8.1.7 and Trio 8500 and 8800 before 7.2.8 allows remote attackers to execute code. HP identifies the affected behavior only as a buffer overflow triggered when Interactive Connectivity Establishment processing is enabled; no public source names the parser, field, or faulty operation. An administrator must enable ICE; once enabled, remote attackers need no authentication or user interaction to execute code on the phone.
The record
- CVE
- CVE-2026-0826
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- Plantronics
- Product
- Poly Trio 8500
- Classifications
- CWE-121, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <7.2.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo