dbcve.org
OrthancApplication · Orthanc Server

CVE-2025-0896

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to 1.5.8 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
Orthanc server prior to version 1.5.8 does not enable basic authentication by default when remote access is enabled. This could result in unauthorized access by an attacker.

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

Orthanc DICOM server versions prior to 1.5.8 do not enable basic authentication by default when remote access is configured, leaving the medical imaging server accessible without any credentials. This allows unauthenticated attackers to access, modify, or exfiltrate sensitive patient imaging data over the network.

MitigationUpgrade to Orthanc 1.5.8 or later, or explicitly configure and enable basic authentication when remote access is required.

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.5.8

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check Orthanc version
    Run 'orthanc --version' or check the installed package version (e.g., dpkg -l | grep orthanc, rpm -qi orthanc)
    Affected if Version is below 1.5.8
  2. Verify if remote access is enabled
    Inspect the Orthanc configuration file (typically /etc/orthanc/orthanc.json) for the 'RemoteAccessAllowed' setting. If using the default configuration, this setting may be absent.
    Affected if RemoteAccessAllowed is set to true or the setting is absent with default behavior allowing remote connections
  3. Confirm authentication status
    In the same configuration file, check the 'AuthenticationEnabled' setting. Also verify if any 'RegisteredUsers' are defined.
    Affected if AuthenticationEnabled is set to false, is absent, or no RegisteredUsers are defined while remote access is permitted
  4. Test network accessibility without credentials
    Attempt to access the Orthanc REST API over HTTP/HTTPS from a remote host (e.g., curl http://<orthanc-host>:8042/server). A successful response without 401 authentication challenge indicates the server is exposed.
    Affected if The server responds with data without requiring HTTP Basic authentication

You are affected if Orthanc version is below 1.5.8, remote access is enabled, and authentication is not explicitly configured/enabled, allowing unauthenticated network access to the DICOM server.

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.5.8 or later
Fixed in 1.5.8
Interim mitigation

Upgrade to Orthanc 1.5.8 or later, or explicitly configure and enable basic authentication when remote access is required.

Recommended fix High confidence

1.5.8

  1. Back up the current Orthanc configuration directory (typically /etc/orthanc or the directory containing orthanc.json)
  2. Stop the Orthanc service
  3. Upgrade Orthanc to version 1.5.8 using the appropriate package manager or build from source (e.g., apt-get install orthanc=1.5.8, yum update orthanc, or compile from orthanc-1.5.8 source)
  4. Start the Orthanc service
  5. Verify that authentication is now enabled by default by checking the 'AuthenticationEnabled' setting in the configuration
  6. Confirm remote access requires valid credentials

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

Fix this in Orthanc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0896 — 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-2025-0896 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