---
id: "CVE-2026-118670"
page: "https://infrastack.ai/live/CVE-2026-118670"
kind: "vulnerability"
aliases: ["CVE-2026-118670"]
title: "OHIF Viewers: crafted DICOM PDF runs script in the viewer's origin"
severity: "high"
cvss: 8.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["dicom", "healthcare", "ohif-viewers", "package", "pacs", "self-hosted"]
not_affected_if: ["dicom-pdf-extension-not-loaded", "version-outside-affected-range"]
published_at: "2026-11-06T18:17:57+00:00"
first_seen_at: "2026-11-06T18:44:08+00:00"
updated_at: "2026-11-06T18:45:14+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-118670", "first_seen_at": "2026-11-06T18:44:08+00:00"}]
exploit_sources: []
---

# OHIF Viewers: crafted DICOM PDF runs script in the viewer's origin

Link for people: https://infrastack.ai/live/CVE-2026-118670 (this .md is for agents)

OHIF Viewers, a web viewer for medical imaging files, renders an embedded PDF inside a DICOM file using a MIME type taken from the file itself. A crafted DICOM object can make the browser treat the embedded document as HTML, so its script runs with the viewer's origin and can reach session storage, auth tokens and same-origin PACS requests.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed `@ohif/viewer` or OHIF app version and compare it with the fixed versions.
- Look for the `dicom-pdf` extension in the deployed build and confirm its version.

## Fix

- Move to `3.12.15`, `3.13.7` or `3.14.0-beta.19` (the fixed source versions in the 3.12, 3.13 and 3.14 lines).

## Timeline

- 2026-11-06T18:44:08+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-118670

## Documents

- [advisory] Vendor advisory: github.com https://github.com/OHIF/Viewers/security/advisories/GHSA-xwgp-w3pj-q5h3
- [fix] Patch: github.com https://github.com/OHIF/Viewers/commit/ef0811c66cdb04ba07ffaba145cf66ce01486899
- [fix] Patch: github.com https://github.com/OHIF/Viewers/commit/f0dba789a313f40fe7e8a8cbec322a8d8a491d76
- [fix] Patch: github.com https://github.com/OHIF/Viewers/commit/db546701bd5f2be9031c835f1de5c40aacd3dc62
- [fix] Release notes: github.com https://github.com/OHIF/Viewers/releases/tag/v3.13.7
- [fix] Release notes: github.com https://github.com/OHIF/Viewers/releases/tag/v3.14.0-beta.19
- [fix] Release notes: github.com https://github.com/OHIF/Viewers/releases/tag/v3.12.15

## From the sources

OHIF Viewers is a zero-footprint DICOM viewer with shared extension packages. From 3.5.0-beta.0 until 3.12.15, 3.13.7, and 3.14.0-beta.19, the dicom-pdf extension reads the attacker-controlled MIMETypeOfEncapsulatedDocument value in extensions/dicom-pdf/src/getSopClassHandlerModule.js and uses it as the Blob media type for the attacker-controlled EncapsulatedDocument bytes. When a victim opens Encapsulated PDF SOP Class 1.2.840.10008.5.1.4.1.1.104.1, extensions/dicom-pdf/src/viewports/OHIFCornerstonePdfViewport.tsx embeds the Blob URL in an object element. A Blob labeled as HTML is handled as HTML despite the application/pdf object hint, and the Blob inherits the OHIF origin, allowing embedded script to access session storage, authentication tokens, and same-origin PACS requests. The malicious DICOM object may be opened locally, uploaded to a shared PACS, or supplied by a DICOMweb source. This issue is fixed in source versions 3.12.15, 3.13.7, and 3.14.0-beta.19.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_