VulnerabilityPublished 10 Nov 2026

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

Affects @ohif/extension-dicom-pdfSource GCVE Database

Compare

Authoritative record:CVE-2026-118670· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 3.12.18 soon.

Data as of 10 Nov 2026, 17:35 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	8.8

Patch: Available – fixed in 3.12.18, 3.13.10, 3.14.0-beta.36

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade @ohif/extension-dicom-pdf to 3.12.18; @ohif/extension-dicom-pdf to 3.13.10; @ohif/extension-dicom-pdf to 3.14.0-beta.36.

Affected software

Product	Affected	Fixed in
npm@ohif/extension-dicom-pdf	Affected >=3.5.0-beta.0 <3.12.18	Fixed in 3.12.18
npm@ohif/extension-dicom-pdf	Affected >=3.13.0-beta.0 <3.13.10	Fixed in 3.13.10
npm@ohif/extension-dicom-pdf	Affected >=3.14.0-beta.0 <3.14.0-beta.36	Fixed in 3.14.0-beta.36

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied by upgrading @ohif/extension-dicom-pdf to version 3.12.18, 3.13.10, or 3.14.0-beta.36 or later. Versions 3.5 through 3.11 will not receive a fix and should be upgraded to a supported patched version. The fix ensures proper validation and handling of the MIMETypeOfEncapsulatedDocument tag to prevent injection of malicious MIME types. No additional mitigations are required if the patch is applied.

Description

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the OHIF Viewers' dicom-pdf extension when rendering Encapsulated PDF DICOM objects. The vulnerability arises from improper validation of the MIMETypeOfEncapsulatedDocument tag, allowing an attacker to control the MIME type of a Blob URL. This can lead to execution of attacker-supplied JavaScript in the context of the OHIF application origin when the victim opens a specially crafted DICOM study. The flaw affects versions prior to 3.12.18, 3.13.10, and 3.14.0-beta.36, with patches available in these and later versions.

Impact

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the OHIF Viewers application origin. This can lead to theft of session tokens, unauthorized access to local storage, and potentially unauthorized requests to the PACS backend. If the OHIF application shares its DNS origin with other applications, those may also be impacted. The vulnerability affects users who open maliciously crafted DICOM Encapsulated PDF objects, potentially leading to session compromise and data exposure.

Summary

The OHIF Viewers' dicom-pdf extension processes the MIMETypeOfEncapsulatedDocument tag from DICOM Encapsulated PDF objects without validation, passing it as the MIME type when creating Blob URLs for rendering. Because browsers use the Blob's stored MIME type to determine how to handle the content, an attacker can supply a MIME type such as 'text/html' to cause the Blob URL to render as HTML. This enables execution of attacker-controlled JavaScript within the OHIF origin, granting access to localStorage, sessionStorage, authentication tokens, and same-origin requests to the PACS. The vulnerability requires the victim to open a study with the Encapsulated PDF SOP Class and the dicom-pdf extension active. The issue is fixed in versions 3.12.18, 3.13.10, and 3.14.0-beta.36 of the @ohif/extension-dicom-pdf package.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 17:35 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats