Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Heap Overflow in Orthanc DICOM Server (CVE‑2026‑87020) Enables Remote Denial‑of‑Service

Orthanc DICOM Server versions prior to 1.13.0 contain an integer‑overflow flaw that lets an authenticated attacker cause a crash via a malicious PNG/JPEG image. The issue highlights the need for rapid patching and verifiable availability controls in healthcare environments.

Verisq™ Intelligence · 📅 September 10, 2026 · 📰 cisa.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
4 recommended
📰
Source
cisa.gov

Heap Overflow in Orthanc DICOM Server (CVE‑2026‑87020) Enables Remote Denial‑of‑Service

What It Is – Orthanc DICOM Server < 1.13.0 contains an integer‑overflow bug in its PNG/JPEG image decoder. An authenticated attacker can craft a malicious image that writes past the end of a heap allocation, crashing the service.

Exploitability – The vulnerability is publicly disclosed (CVE‑2026‑87020) with a CVSS 3.1 base score of 8.1 (High). No public exploit code is known, but the attack requires only network access and valid credentials.

Affected Products – Orthanc DICOM Server versions prior to 1.13.0 (vendor: Orthanc, Belgium).

Why It Matters for Trust & Control Assurance

  • Patch Management & Evidence – Demonstrating timely remediation of high‑severity flaws is a core control objective; continuous monitoring of patch status provides audit‑ready evidence.
  • Availability Controls – A DoS condition on a medical imaging server can interrupt patient care workflows; controls around system resilience and incident logging must be verifiable.
  • Supply‑Chain Assurance – Orthanc is widely deployed in healthcare; third‑party risk programs need to capture vulnerability exposure and remediation proof for downstream auditors.

Recommended Actions

  1. Upgrade all Orthanc instances to version 1.13.0 or later.
  2. Verify the patch by scanning for the CVE identifier and confirming the version number.
  3. Enable process‑level monitoring (e.g., crash‑dump collection, health‑check alerts) to detect any attempted exploitation.
  4. Document the remediation in your vulnerability‑management system to provide defensible evidence for audits.

Source: CISA Advisory – ICSMA‑26‑253‑02

📰 Original Source
https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-253-02 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →