CVE-2022-2119

CRITICALNVD 7.59.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-06-25. NVD baseline CVSS 7.5; sources differ by 2.3.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2022-34405 (ENISA EUVD) · GHSA-5pjf-38m2-65rx (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

OFFIS DCMTK's (All versions prior to 3.6.7) service class provider (SCP) is vulnerable to path traversal, allowing an attacker to write DICOM files into arbitrary directories under controlled names. This could allow remote code execution.

CVSS v3
7.5
EG Score
9.8CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation3.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.4%
EPSS %ILE
88th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
3.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 24, 2022

Last Modified

November 3, 2025

Advisory Details (2)

Auto-updated Oct 13, 2026
Patch available. Sources: cisa.
CISA

OFFIS DCMTK | CISA

https://www.cisa.gov/uscert/ics/advisories/icsma-22-174-01
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4227-1] dcmtk security update

https://lists.debian.org/debian-lts-announce/2025/06/msg00025.html

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibdcmtk-dev (3.6.1~20150924-5ubuntu0.1~esm1) @ xenial2026-11-02ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
dcmtk3.6.5-1, 3.6.5-1+deb11u1, 3.6.5-1+deb11u2, 3.6.5-1+deb11u3
  • every version up to 3.6.5-1+deb11u4: fixed in 3.6.5-1+deb11u4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dcmtk—
  • every version up to 3.6.7-6: fixed in 3.6.7-6
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dcmtk—
  • every version up to 3.6.7-6: fixed in 3.6.7-6
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dcmtk—
  • every version up to 3.6.7-6: fixed in 3.6.7-6
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 30× in last 7d / 94× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 269 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 169 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-2119?
CVE-2022-2119 is a critical-severity vulnerability; its CVE record was published on June 24, 2022. OFFIS DCMTK's (All versions prior to 3.6.7) service class provider (SCP) is vulnerable to path traversal, allowing an attacker to write DICOM files into arbitrary directories under controlled names. This could allow remote code execution.
When was CVE-2022-2119 made public?
CVE-2022-2119 was made public on June 23, 2022: that is the date its CVE record's CNA, Cybersecurity and Infrastructure Security Agency (CISA) Industrial Control Systems (ICS), gives for when the vulnerability was made public. The CVE record itself was published on June 24, 2022. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2022-2119 actively exploited?
CVE-2022-2119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.4% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-2119?
CVE-2022-2119 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-2119?
A fix for CVE-2022-2119 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-2119

Explore →

Is Your Infrastructure Affected by CVE-2022-2119?

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

Book a Demo →Browse All CVEs