CVE-2026-22879

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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

A heap-based buffer overflow vulnerability exists in the vtkDICOMItem::FindDataElementOrInsert functionality of vtk-dicom (version(s): 9.5.2). A specially crafted DICOM file can lead to heap-based memory corruption. An attacker can provide a malicious file to trigger this vulnerability.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

Published

June 25, 2026

Last Modified

September 23, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
No fix on record yet.
generic

TALOS-2026-2366 || Cisco Talos Intelligence Group - Comprehensive Threat Intelligence

https://talosintelligence.com/vulnerability_reports/TALOS-2026-2366

Vendor Advisories for CVE-2026-22879(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
vtk-dicom0.8.12-4 ... 0.8.17-3 (11 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
vtk-dicom0.8.14-3.1, 0.8.14-3.2~exp1, 0.8.17-1, 0.8.17-2, 0.8.17-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
vtk-dicom0.8.17-1, 0.8.17-2, 0.8.17-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
vtk-dicom0.8.17-1, 0.8.17-2, 0.8.17-3
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 35× 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.

Showing the most recent 100 of 251 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-29 15:21 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:47 UTCEPSS rescore
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 00:26 UTCEPSS rescore
  15. 2026-09-24 14:03 UTCEPSS rescore
  16. 2026-09-23 11:23 UTCEG score recompute
  17. 2026-09-23 11:23 UTCGHSA enrichment
  18. 2026-09-23 11:01 UTCEG score recompute
  19. 2026-09-23 11:01 UTCGHSA enrichment
  20. 2026-09-23 08:24 UTCEG score recompute
  21. 2026-09-23 08:24 UTCGHSA enrichment
  22. 2026-09-20 20:15 UTCEPSS rescore
  23. 2026-09-18 19:27 UTCEPSS rescore
  24. 2026-09-18 07:19 UTCEG score recompute
  25. 2026-09-18 07:19 UTCGHSA enrichment
Show 75 more
  1. 2026-09-16 14:07 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-14 01:16 UTCEG score recompute
  4. 2026-09-14 01:16 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-13 09:36 UTCGHSA enrichment
  7. 2026-09-12 15:41 UTCEG score recompute
  8. 2026-09-12 15:41 UTCGHSA enrichment
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:52 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-04 05:06 UTCEPSS rescore
  17. 2026-09-02 14:11 UTCEPSS rescore
  18. 2026-09-01 13:53 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:27 UTCEG score recompute
  21. 2026-08-30 19:27 UTCGHSA enrichment
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 01:22 UTCEPSS rescore
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-27 23:15 UTCEG score recompute
  26. 2026-08-27 23:15 UTCGHSA enrichment
  27. 2026-08-27 14:25 UTCEPSS rescore
  28. 2026-08-26 14:46 UTCEPSS rescore
  29. 2026-08-25 13:48 UTCEPSS rescore
  30. 2026-08-25 01:30 UTCEG score recompute
  31. 2026-08-25 01:30 UTCGHSA enrichment
  32. 2026-08-24 13:08 UTCEG score recompute
  33. 2026-08-24 13:08 UTCGHSA enrichment
  34. 2026-08-23 23:10 UTCGHSA enrichment
  35. 2026-08-23 10:40 UTCEG score recompute
  36. 2026-08-23 10:40 UTCGHSA enrichment
  37. 2026-08-23 00:19 UTCEPSS rescore
  38. 2026-08-22 22:18 UTCGHSA enrichment
  39. 2026-08-22 09:55 UTCEG score recompute
  40. 2026-08-22 09:55 UTCGHSA enrichment
  41. 2026-08-21 23:49 UTCEPSS rescore
  42. 2026-08-21 20:06 UTCGHSA enrichment
  43. 2026-08-21 07:44 UTCEG score recompute
  44. 2026-08-21 07:44 UTCGHSA enrichment
  45. 2026-08-20 22:55 UTCEPSS rescore
  46. 2026-08-20 19:22 UTCGHSA enrichment
  47. 2026-08-20 07:00 UTCEG score recompute
  48. 2026-08-20 07:00 UTCGHSA enrichment
  49. 2026-08-19 17:03 UTCEPSS rescore
  50. 2026-08-19 13:34 UTCGHSA enrichment
  51. 2026-08-19 01:12 UTCEG score recompute
  52. 2026-08-19 01:12 UTCGHSA enrichment
  53. 2026-08-18 13:48 UTCEPSS rescore
  54. 2026-08-17 13:47 UTCEPSS rescore
  55. 2026-08-17 13:44 UTCGHSA enrichment
  56. 2026-08-17 01:22 UTCEG score recompute
  57. 2026-08-17 01:22 UTCGHSA enrichment
  58. 2026-08-16 14:56 UTCEPSS rescore
  59. 2026-08-16 13:00 UTCEG score recompute
  60. 2026-08-16 13:00 UTCGHSA enrichment
  61. 2026-08-16 02:14 UTCEPSS rescore
  62. 2026-08-16 00:38 UTCGHSA enrichment
  63. 2026-08-15 12:16 UTCEG score recompute
  64. 2026-08-15 12:16 UTCGHSA enrichment
  65. 2026-08-15 01:30 UTCEPSS rescore
  66. 2026-08-14 23:53 UTCGHSA enrichment
  67. 2026-08-14 11:31 UTCGHSA enrichment
  68. 2026-08-13 23:09 UTCEG score recompute
  69. 2026-08-13 23:09 UTCGHSA enrichment
  70. 2026-08-13 22:00 UTCEPSS rescore
  71. 2026-08-13 10:42 UTCGHSA enrichment
  72. 2026-08-12 22:20 UTCEG score recompute
  73. 2026-08-12 22:20 UTCGHSA enrichment
  74. 2026-08-12 13:50 UTCEPSS rescore
  75. 2026-08-12 09:58 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-22879?
CVE-2026-22879 is a high vulnerability published on June 25, 2026. A heap-based buffer overflow vulnerability exists in the vtkDICOMItem::FindDataElementOrInsert functionality of vtk-dicom (version(s): 9.5.2). A specially crafted DICOM file can lead to heap-based memory corruption. An attacker can provide a malicious file to trigger this vulnerability.
When was CVE-2026-22879 disclosed?
CVE-2026-22879 was first published on June 25, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22879 actively exploited?
CVE-2026-22879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-22879?
CVE-2026-22879 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-22879?
No fix for CVE-2026-22879 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-22879 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-22879

Explore →

Is Your Infrastructure Affected by CVE-2026-22879?

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

Book a Demo →Browse All CVEs