CVE-2026-50003

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-01. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

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

A malicious or compromised server can make a DCMTK client using bit-preserving C-GET storage mode write files outside the chosen output directory, using both relative (../) paths and absolute paths.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
35.0%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 1, 2026

Advisory Details (3)

Auto-updated Jul 3, 2026
Patch available. Sources: github_release, cisa.
cisa Patch Available

OFFIS DCMTK Toolkit | CISA

https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-181-01
generic

CSAF/csaf_files/OT/white/2026/icsma-26-181-01.json at develop · cisagov/CSAF · GitHub

https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsma-26-181-01.json
github_release Patch Available

DCMTK-3.7.0

Patch available: DCMTK/dcmtk DCMTK-3.7.0

https://github.com/DCMTK/dcmtk/releases/tag/latest

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

Frequently asked(5)

What is CVE-2026-50003?
CVE-2026-50003 is a critical vulnerability published on June 30, 2026. A malicious or compromised server can make a DCMTK client using bit-preserving C-GET storage mode write files outside the chosen output directory, using both relative (../) paths and absolute paths.
When was CVE-2026-50003 disclosed?
CVE-2026-50003 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50003 actively exploited?
CVE-2026-50003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50003?
CVE-2026-50003 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-50003?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50003, 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-50003

Explore →

Is Your Infrastructure Affected by CVE-2026-50003?

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