CVE-2026-2891

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The following Poly Voice IP devices, CCX, Trio, and Edge E, might be inoperable if they connect to a malicious SIP server and receive malformed data. HP is releasing updates to mitigate these potential vulnerabilities.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Vendor Advisories for CVE-2026-2891(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 83× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 11:53 UTCGHSA enrichment
  2. 2026-07-27 00:59 UTCEG score recompute
  3. 2026-07-27 00:59 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 13:19 UTCEG score recompute
  7. 2026-07-26 13:19 UTCGHSA enrichment
  8. 2026-07-25 14:18 UTCEPSS rescore
  9. 2026-07-25 14:17 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:08 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:24 UTCEPSS rescore
  17. 2026-07-21 15:24 UTCEPSS rescore
  18. 2026-07-20 17:08 UTCEPSS rescore
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 14:31 UTCEPSS rescore
  21. 2026-07-19 14:31 UTCEPSS rescore
  22. 2026-07-19 02:29 UTCEPSS rescore
  23. 2026-07-18 10:04 UTCEPSS rescore
  24. 2026-07-18 10:04 UTCEPSS rescore
  25. 2026-07-17 04:21 UTCGHSA enrichment
Show 58 more
  1. 2026-07-16 17:29 UTCGHSA enrichment
  2. 2026-07-16 17:03 UTCEPSS rescore
  3. 2026-07-16 17:03 UTCEPSS rescore
  4. 2026-07-16 05:36 UTCGHSA enrichment
  5. 2026-07-15 18:43 UTCGHSA enrichment
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 07:49 UTCGHSA enrichment
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-14 20:57 UTCGHSA enrichment
  12. 2026-07-14 10:03 UTCGHSA enrichment
  13. 2026-07-13 23:10 UTCGHSA enrichment
  14. 2026-07-13 22:30 UTCEPSS rescore
  15. 2026-07-13 12:17 UTCGHSA enrichment
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 01:20 UTCGHSA enrichment
  19. 2026-07-12 14:26 UTCGHSA enrichment
  20. 2026-07-12 05:46 UTCEPSS rescore
  21. 2026-07-12 03:32 UTCGHSA enrichment
  22. 2026-07-11 16:39 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 05:46 UTCGHSA enrichment
  25. 2026-07-10 18:54 UTCGHSA enrichment
  26. 2026-07-10 08:01 UTCGHSA enrichment
  27. 2026-07-09 21:07 UTCGHSA enrichment
  28. 2026-07-09 19:10 UTCEPSS rescore
  29. 2026-07-09 10:15 UTCGHSA enrichment
  30. 2026-07-08 23:22 UTCGHSA enrichment
  31. 2026-07-08 15:15 UTCEPSS rescore
  32. 2026-07-08 12:30 UTCGHSA enrichment
  33. 2026-07-08 01:33 UTCGHSA enrichment
  34. 2026-07-07 14:41 UTCGHSA enrichment
  35. 2026-07-07 13:46 UTCEPSS rescore
  36. 2026-07-07 03:44 UTCGHSA enrichment
  37. 2026-07-06 16:51 UTCGHSA enrichment
  38. 2026-07-06 16:27 UTCEPSS rescore
  39. 2026-07-06 16:27 UTCEPSS rescore
  40. 2026-07-06 05:58 UTCGHSA enrichment
  41. 2026-07-06 02:23 UTCEPSS rescore
  42. 2026-07-06 02:23 UTCEPSS rescore
  43. 2026-07-05 19:04 UTCGHSA enrichment
  44. 2026-07-05 08:11 UTCGHSA enrichment
  45. 2026-07-05 02:30 UTCEPSS rescore
  46. 2026-07-04 21:18 UTCGHSA enrichment
  47. 2026-07-04 10:26 UTCGHSA enrichment
  48. 2026-07-04 06:31 UTCEPSS rescore
  49. 2026-07-03 23:33 UTCGHSA enrichment
  50. 2026-07-03 12:41 UTCGHSA enrichment
  51. 2026-07-03 01:47 UTCGHSA enrichment
  52. 2026-07-02 14:54 UTCGHSA enrichment
  53. 2026-07-02 04:02 UTCGHSA enrichment
  54. 2026-07-01 17:08 UTCEG score recompute 8.20
  55. 2026-07-01 17:08 UTCGHSA enrichment
  56. 2026-07-01 17:06 UTCNVD updateCVSS v3 → 8.2 · CVSS v4 → 8.2
  57. 2026-07-01 16:04 UTCEG score recompute
  58. 2026-07-01 16:03 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-2891?
CVE-2026-2891 is a high vulnerability published on July 1, 2026. The following Poly Voice IP devices, CCX, Trio, and Edge E, might be inoperable if they connect to a malicious SIP server and receive malformed data. HP is releasing updates to mitigate these potential vulnerabilities.
When was CVE-2026-2891 disclosed?
CVE-2026-2891 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2891 actively exploited?
CVE-2026-2891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.3% of all scored CVEs.
What is the CVSS score of CVE-2026-2891?
CVE-2026-2891 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-2891?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2891, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-2891

Explore →

Is Your Infrastructure Affected by CVE-2026-2891?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.