CVE-2026-12473
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTwo data sources (DICOMWebProxy and DICOMJSON) shipped in the default configuration fetch an arbitrary URL parameter without validation. A global authentication service in OHIF automatically injects the authenticated user's OIDC Bearer token into the resulting requests, sending it to the attacker-controlled server. DICOMweb data sources are not impacted.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOHIF's DICOMWebProxy and DICOMJSON data sources fetch arbitrary URLs from parameters without validation. When a user is authenticated via OIDC, OHIF's global authentication service automatically appends the user's Bearer token to these requests, enabling attackers to steal authentication credentials by tricking users into visiting malicious URLs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OHIF installation and versionLocate the OHIF package (typically in node_modules/@ohif/viewer or similar) and check package.json for the installed version number, or run 'npm list @ohif/viewer' in the project directoryAffected if The installed version is within the affected range and the specific version is unpatched for CVE-2026-12473
-
Confirm DICOMWebProxy or DICOMJSON data source is configuredExamine the OHIF configuration file (usually default.js, config.js, or a custom configuration) for entries using 'dicomweb' or 'dicomjson' as the data source type in the 'dataSources' arrayAffected if Either DICOMWebProxy or DICOMJSON data source is defined in the configuration
-
Verify OIDC authentication is enabledCheck the OHIF configuration for oidc section or OAuth2/OIDC provider settings (look for 'oidc', 'auth', or 'oauth' configuration keys) that enable bearer token-based authenticationAffected if OIDC/OAuth2 authentication is configured and active, causing tokens to be automatically attached to requests
-
Check for URL validation in data source configurationInspect the data source configuration parameters for any whitelist, validation logic, or restriction on the 'wadoUri', 'qidoRoot', or 'wadoRoot' URL parameters that would prevent arbitrary URL injectionAffected if No URL validation or whitelist is present, allowing arbitrary URLs to be specified in data source parameters
-
Confirm automatic token injection behaviorReview the OHIF source code or authentication configuration to determine whether bearer tokens are automatically appended to all outbound requests from data sources, or if token inclusion requires explicit opt-in configurationAffected if Tokens are automatically appended to requests made by data sources without explicit opt-in for each outbound request
A user is affected if running a vulnerable OHIF version with DICOMWebProxy or DICOMJSON data sources, OIDC authentication enabled, no URL validation on data source URLs, and automatic token injection into outbound requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataValidate and whitelist URLs permitted in data source configuration; implement explicit opt-in for token inclusion in outbound requests rather than automatic injection.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12473 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data