Skip to content

← Actionable
High, CVSS 8.8amended

OHIF Viewers: DOM-Based Cross Site Scripting (XSS) through MIME type of document

CVE-2026-118670GHSA-xwgp-w3pj-q5h3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@ohif/extension-dicom-pdf 3.14.0-beta.36, 3.13.10, 3.12.18), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm @ohif/extension-dicom-pdf

    Affected
    >= 3.5.0-beta.0, < 3.12.18>= 3.13.0-beta.0, < 3.13.10>= 3.14.0-beta.0, < 3.14.0-beta.36
    Fixed in
    3.13.10, 3.14.0-beta.36, 3.12.18

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L
EPSS
  • CVE-2026-118670: 0.42% estimated exploitation activity in the next 30 days; percentile 36.69 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary An XSS (Cross-Site Scripting) vulnerability occurs when an attacker is able to inject their own JavaScript code into a web page's source, which is subsequently processed by the victim's browser. A common cause of this vulnerability is the failure to validate user-supplied data before displaying it within the vulnerable application without proper filtering. To exploit the vulnerability, an attacker must input HTML code into a vulnerable parameter containing structures that trigger the execution of JavaScript. The DOM XSS variant occurs when user-supplied data is processed by a client-side script; if this data is not handled correctly by the script itself, it becomes possible to inject additional JavaScript commands. Attacker model: Any actor who can get a DICOM object in front of a victim — email a `.dcm` for local viewing, upload to a shared PACS, or operate/compromise a DICOMweb source. Preconditions: Victim opens a study whose SOP Class is Encapsulated PDF…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-xwgp-w3pj-q5h3

  2. Revision 1 · created ·

    Published from ghsa record GHSA-xwgp-w3pj-q5h3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-118670

Advisory: OHIF Viewers: DOM-Based Cross Site Scripting (XSS) through MIME type of document
IDs: CVE-2026-118670, GHSA-xwgp-w3pj-q5h3
Record: https://patchnext.com/advisories/cve-2026-118670 (revision 2, source checked 11 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @ohif/extension-dicom-pdf 3.14.0-beta.36, 3.13.10, 3.12.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @ohif/extension-dicom-pdf: affected >= 3.5.0-beta.0, < 3.12.18; >= 3.13.0-beta.0, < 3.13.10; >= 3.14.0-beta.0, < 3.14.0-beta.36; fixed in 3.13.10, 3.14.0-beta.36, 3.12.18

## Suggested inspection (read-only)
- `npm ls @ohif/extension-dicom-pdf --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @ohif/extension-dicom-pdf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xwgp-w3pj-q5h3 (GitHub-reviewed advisory GHSA-xwgp-w3pj-q5h3 lists affected ranges: npm @ohif/extension-dicom-pdf >=3.5.0-beta.0 =3.13.0-beta.0 =3.14.0-beta.0 <3.14.0-beta.36)
- Verified: https://osv.dev/vulnerability/GHSA-xwgp-w3pj-q5h3 (OSV record GHSA-xwgp-w3pj-q5h3 lists affected ranges: npm @ohif/extension-dicom-pdf >=3.5.0-beta.0 =3.13.0-beta.0 =3.14.0-beta.0 <3.14.0-beta.36 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…