dbcve.org
OrthancApplication · Orthanc Server

CVE-2026-5445

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 1.12.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An out-of-bounds read vulnerability exists in the `DecodeLookupTable` function within `DicomImageDecoder.cpp`. The lookup-table decoding logic used for `PALETTE COLOR` images does not validate pixel indices against the lookup table size. Crafted images containing indices larger than the palette size cause the decoder to read beyond allocated lookup table memory and expose heap contents in the output image.

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 confidence

An out-of-bounds read vulnerability exists in the DecodeLookupTable function within DicomImageDecoder.cpp. The lookup-table decoding logic for PALETTE COLOR images fails to validate pixel indices against the lookup table size, allowing crafted DICOM images with indices exceeding the palette size to read beyond allocated memory and expose heap contents in the output image.

MitigationImplement bounds checking to validate all pixel indices against the lookup table size before memory access, or disable PALETTE COLOR image decoding until a patch is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OrthancApplication
Affected:< 1.12.11

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Orthanc Server version
    Run 'orthanc --version' or check the Orthanc logs/UI for the version number, or query the /system endpoint of the Orthanc REST API
    Affected if The version number is less than 1.12.11 (e.g., 1.12.10, 1.12.0, or any 1.x.x version below 1.12.11)
  2. Confirm DICOM PALETTE COLOR image processing is enabled
    Check if Orthanc is configured to accept and process DICOM files. Review configuration for enabled modalities or storage of DICOM instances
    Affected if Orthanc is actively processing incoming DICOM images (PALETTE COLOR type specifically triggers the vulnerable code path)
  3. Check for recent incoming PALETTE COLOR DICOM images
    Review Orthanc storage or logs for recent instances with photometric interpretation of PALETTE COLOR, or query the database for instances where PhotometricInterpretation contains 'PALETTE COLOR'
    Affected if PALETTE COLOR DICOM images have been stored or processed by the Orthanc instance

The environment is affected if Orthanc Server version is below 1.12.11 and the server processes or has processed PALETTE COLOR DICOM images, as the DecodeLookupTable function will attempt out-of-bounds reads when pixel indices exceed the lookup table size.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.12.11 or later
Fixed in 1.12.11
Interim mitigation

Implement bounds checking to validate all pixel indices against the lookup table size before memory access, or disable PALETTE COLOR image decoding until a patch is applied.

Recommended fix High confidence

Orthanc 1.12.11 or later

  1. 1. Identify the current Orthanc version by running `orthanc --version` or checking the package manager
  2. 2. Stop the Orthanc service: `sudo systemctl stop orthanc` or `sudo service orthanc stop`
  3. 3. For Debian/Ubuntu: Update package lists with `sudo apt update`, then install the fixed version with `sudo apt install orthanc=1.12.11`
  4. 4. For RHEL/CentOS: Run `sudo yum update orthanc` or `sudo dnf update orthanc`
  5. 5. For source builds: Download Orthanc 1.12.11 from the official Orthanc Server website or GitHub releases page
  6. 6. Rebuild and reinstall Orthanc from source if using a custom build
  7. 7. Verify the new version is installed: `orthanc --version`
  8. 8. Restart the Orthanc service: `sudo systemctl start orthanc` or `sudo service orthanc start`

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Orthanc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5445 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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