CVE-2026-0754: HP VVX · CWE-321
Affects HP VVXSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to <UCS 6.4.8 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in <UCS 6.4.8, <PVOS 8.5.0, <UCS 8.1.7.c
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade VVX to <UCS 6.4.8; Edge E to <PVOS 8.5.0; Trio 8300 to <UCS 8.1.7.c.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HP IncVVX | Affected
| Fixed in
|
| HP IncEdge E | Affected
| Fixed in
|
| HP IncTrio 8300 | Affected
| Fixed in
|
AI-suggested
Organizations should immediately audit their SIP service provider's certificate validation processes to ensure strict verification of device certificates, rejecting any that do not meet expected criteria. HP Inc and affected customers should monitor for official firmware updates or patches addressing this embedded test key vulnerability and apply them promptly once available. If you cannot patch yet, organizations should consider network segmentation and strict physical security controls to limit access to VVX devices and prevent unauthorized firmware extraction. Deploying network-level authentication and anomaly detection for SIP traffic can help identify and block unauthorized devices attempting to connect. Additionally, organizations should review and harden their VoIP infrastructure configurations, including disabling legacy or test modes on devices and enforcing mutual TLS authentication where possible. Regular security assessments and penetration testing focused on VoIP devices can help detect similar embedded keys or misconfigurations. Finally, educating staff about the risks of device tampering and insider threats can reduce the likelihood of local exploitation.
Description
An embedded test key and certificate could be extracted from a Poly Voice device using specialized reverse engineering tools. This extracted certificate could be accepted by a SIP service provider if the service provider does not perform proper validation of the device certificate.