CVE-2026-5923

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: None knownExposed: 0

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

Malicious use of a stolen cookie might allow modifications to the contents of the IP phone’s webpage.

CVSS v3
6.0
EG Score
6.0(medium)
EG Risk
27(Track)
EG Risk 27/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
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Vendor Advisories for CVE-2026-5923(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 19× in last 7d / 55× 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-08-02 02:27 UTCEPSS rescore
  2. 2026-08-01 04:16 UTCEPSS rescore
  3. 2026-08-01 01:46 UTCGHSA enrichment
  4. 2026-07-30 23:15 UTCEG score recompute
  5. 2026-07-30 23:15 UTCGHSA enrichment
  6. 2026-07-30 16:28 UTCEPSS rescore
  7. 2026-07-30 01:30 UTCEPSS rescore
  8. 2026-07-30 01:30 UTCEPSS rescore
  9. 2026-07-29 21:17 UTCGHSA enrichment
  10. 2026-07-28 17:39 UTCEG score recompute
  11. 2026-07-28 17:39 UTCGHSA enrichment
  12. 2026-07-28 15:37 UTCEPSS rescore
  13. 2026-07-27 15:38 UTCEG score recompute
  14. 2026-07-27 15:38 UTCGHSA enrichment
  15. 2026-07-27 14:14 UTCEPSS rescore
  16. 2026-07-26 14:54 UTCEPSS rescore
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 12:23 UTCEG score recompute
  19. 2026-07-26 12:23 UTCGHSA enrichment
  20. 2026-07-25 14:18 UTCEPSS rescore
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-24 14:18 UTCEPSS rescore
  23. 2026-07-24 14:18 UTCEPSS rescore
  24. 2026-07-23 14:18 UTCEPSS rescore
  25. 2026-07-23 14:18 UTCEPSS rescore
Show 30 more
  1. 2026-07-23 03:21 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 11:31 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 09:32 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 07:30 UTCGHSA enrichment
  17. 2026-07-13 22:31 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 05:32 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-12 03:34 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-11 01:35 UTCGHSA enrichment
  26. 2026-07-09 23:36 UTCGHSA enrichment
  27. 2026-07-09 19:10 UTCEPSS rescore
  28. 2026-07-09 19:10 UTCEPSS rescore
  29. 2026-07-08 21:39 UTCEG score recompute
  30. 2026-07-08 21:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-5923?
CVE-2026-5923 is a medium vulnerability published on July 8, 2026. Malicious use of a stolen cookie might allow modifications to the contents of the IP phone’s webpage.
When was CVE-2026-5923 disclosed?
CVE-2026-5923 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5923 actively exploited?
CVE-2026-5923 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 96.2% of all scored CVEs.
What is the CVSS score of CVE-2026-5923?
CVE-2026-5923 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-5923?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5923, 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-5923

Explore →

Is Your Infrastructure Affected by CVE-2026-5923?

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