CVE-2026-34917

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-06-23. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

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

Low‑privileged session IDs generated for the web admin console could be reused in the XML‑RPC API, whose authentication is normally restricted to admin users. An attacker could leverage this to gain unauthorised access and exploit API‑level vulnerabilities. The session context (web/API) is now recorded along with other session data, preventing session IDs from being used interchangeably.

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

Published

June 23, 2026

Last Modified

June 25, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-34917(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 / 61× 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-31 03:39 UTCEG score recompute
  2. 2026-07-31 03:39 UTCGHSA enrichment
  3. 2026-07-30 16:28 UTCEPSS rescore
  4. 2026-07-30 02:35 UTCEG score recompute
  5. 2026-07-30 02:35 UTCGHSA enrichment
  6. 2026-07-30 01:30 UTCEPSS rescore
  7. 2026-07-29 01:16 UTCEG score recompute
  8. 2026-07-29 01:16 UTCGHSA enrichment
  9. 2026-07-27 17:46 UTCEG score recompute
  10. 2026-07-27 17:46 UTCGHSA enrichment
  11. 2026-07-27 14:13 UTCEPSS rescore
  12. 2026-07-26 15:53 UTCEG score recompute
  13. 2026-07-26 15:53 UTCGHSA enrichment
  14. 2026-07-26 14:54 UTCEPSS rescore
  15. 2026-07-26 14:54 UTCEPSS rescore
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-25 14:18 UTCEPSS rescore
  18. 2026-07-24 14:17 UTCEPSS rescore
  19. 2026-07-24 14:17 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 14:18 UTCEPSS rescore
  22. 2026-07-23 03:09 UTCEG score recompute
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-21 15:24 UTCEPSS rescore
  25. 2026-07-20 17:08 UTCEPSS rescore
Show 58 more
  1. 2026-07-19 14:31 UTCEPSS rescore
  2. 2026-07-19 02:29 UTCEPSS rescore
  3. 2026-07-18 10:04 UTCEPSS rescore
  4. 2026-07-16 17:59 UTCGHSA enrichment
  5. 2026-07-16 17:03 UTCEPSS rescore
  6. 2026-07-15 16:57 UTCEPSS rescore
  7. 2026-07-15 16:57 UTCEPSS rescore
  8. 2026-07-15 16:27 UTCGHSA enrichment
  9. 2026-07-15 02:00 UTCEPSS rescore
  10. 2026-07-14 17:34 UTCGHSA enrichment
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 18:41 UTCGHSA enrichment
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-12 19:48 UTCGHSA enrichment
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 20:54 UTCGHSA enrichment
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-10 22:01 UTCGHSA enrichment
  20. 2026-07-09 23:07 UTCGHSA enrichment
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 00:14 UTCGHSA enrichment
  23. 2026-07-08 15:15 UTCEPSS rescore
  24. 2026-07-08 01:21 UTCGHSA enrichment
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-07 02:26 UTCGHSA enrichment
  27. 2026-07-06 16:27 UTCEPSS rescore
  28. 2026-07-06 16:27 UTCEPSS rescore
  29. 2026-07-06 03:32 UTCGHSA enrichment
  30. 2026-07-06 02:23 UTCEPSS rescore
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-05 04:32 UTCGHSA enrichment
  33. 2026-07-05 02:30 UTCEPSS rescore
  34. 2026-07-04 05:37 UTCGHSA enrichment
  35. 2026-07-03 06:42 UTCGHSA enrichment
  36. 2026-07-02 07:46 UTCGHSA enrichment
  37. 2026-07-01 15:06 UTCEPSS rescore
  38. 2026-07-01 08:53 UTCGHSA enrichment
  39. 2026-06-30 23:22 UTCEPSS rescore
  40. 2026-06-30 09:59 UTCGHSA enrichment
  41. 2026-06-29 14:06 UTCEPSS rescore
  42. 2026-06-29 14:06 UTCEPSS rescore
  43. 2026-06-29 10:57 UTCGHSA enrichment
  44. 2026-06-28 14:07 UTCEPSS rescore
  45. 2026-06-28 14:07 UTCEPSS rescore
  46. 2026-06-28 12:04 UTCGHSA enrichment
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-28 04:56 UTCEPSS rescore
  49. 2026-06-27 13:10 UTCGHSA enrichment
  50. 2026-06-27 03:08 UTCEPSS rescore
  51. 2026-06-26 14:17 UTCGHSA enrichment
  52. 2026-06-25 15:23 UTCGHSA enrichment
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-25 13:49 UTCEPSS rescore
  55. 2026-06-24 16:29 UTCGHSA enrichment
  56. 2026-06-24 14:05 UTCEPSS rescore
  57. 2026-06-23 17:36 UTCEG score recompute
  58. 2026-06-23 17:34 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-34917?
CVE-2026-34917 is a medium vulnerability published on June 23, 2026. Low‑privileged session IDs generated for the web admin console could be reused in the XML‑RPC API, whose authentication is normally restricted to admin users. An attacker could leverage this to gain unauthorised access and exploit API‑level vulnerabilities. The session context (web/API) is now…
When was CVE-2026-34917 disclosed?
CVE-2026-34917 was first published in the National Vulnerability Database on June 23, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34917 actively exploited?
CVE-2026-34917 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 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-34917?
CVE-2026-34917 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-34917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34917, 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-34917

Explore →

Is Your Infrastructure Affected by CVE-2026-34917?

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