OHIF DICOM Viewer SSRF leaks auth tokens
A server-side request forgery flaw in OHIF DICOM Web Viewer Framework ≤v3.12.0 lets attackers steal clinician authentication tokens via crafted links, affecting healthcare deployments worldwide.
Sourcecisa.gov — open the original
What to check
- Applies to
- The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CISA has disclosed CVE-2026-12473, a server-side request forgery vulnerability in the OHIF DICOM Web Viewer Framework versions 3.12.0 and earlier. Two data sources (DICOMWebProxy and DICOMJSON) shipped in the default configuration fetch arbitrary URL parameters without validation. The framework's global authentication service automatically injects authenticated users' OIDC Bearer tokens into these requests, transmitting credentials to attacker-controlled servers when victims follow crafted links.
The Open Health Imaging Foundation released version 3.12.2 on 2026-05-18 to address the vulnerability. Organizations using OHIF with authentication must upgrade and, if they require dicomwebproxy or dicomjson in authenticated deployments, configure the new dangerouslyAllowedOriginsForAuthenticatedEnvironments allowlist. CISA recommends removing all unused DicomWebProxyDataSource and DicomJSONDataSource configurations from deployment files.
The vulnerability affects healthcare imaging systems deployed worldwide. While no active exploitation has been reported to CISA, the potential for credential theft in clinical environments poses significant risks to patient data confidentiality and system integrity. Simon Weber and Volker Schönefeld of Machine Spirits UG reported the vulnerability to CISA.
Mentioned in this report
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsma-26-176-02
Free public brief. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them, no card.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs