dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-0611

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Spacelabs Healthcare Sentinel versions 10.5.x and higher and 11.x.x before 11.6.0 contain an unauthenticated remote code execution vulnerability through a deprecated .NET Remoting HTTP channel exposed on port 8989 that allows attackers to perform arbitrary file read and write operations by supplying valid .NET URI endpoints. Attackers can write ASPX webshells to the IIS wwwroot directory to achieve unauthenticated remote code execution on the system. Port 8989 is not exposed in a default Sentinel installation; exploitation requires that the .NET Remoting port has been explicitly made network-accessible through deliberate configuration or network policy changes.

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

Spacelabs Healthcare Sentinel contains an unauthenticated RCE vulnerability in deprecated .NET Remoting HTTP channels listening on port 8989. When this port is made network-accessible (non-default), attackers can supply malicious .NET URI endpoints to perform arbitrary file read/write operations, including writing ASPX webshells to the IIS wwwroot directory for full system compromise.

MitigationImmediately restrict or block network access to port 8989 via firewall rules or network segmentation if exposed, and apply vendor patches (version 11.6.0 or later) when available.

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
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. Determine Sentinel version
    Use the product's built-in version check mechanism (typically found in the software itself, About section, or installation directory) to identify the installed Sentinel version number.
    Affected if The installed version is 10.5.x or 11.x (any minor version) and is below 11.6.0.
  2. Verify port 8989 is listening
    Run 'netstat -an | findstr 8989' or 'ss -tlnp | grep 8989' on the Sentinel server to confirm the .NET Remoting HTTP channel is bound and listening.
    Affected if Port 8989 shows as LISTENING, indicating the vulnerable service is active.
  3. Confirm network exposure of port 8989
    From an external host or non-internal network position, attempt to reach the Sentinel server on port 8989 (e.g., using telnet, nc, or PowerShell Test-NetConnection). Check firewall rules for any inbound allowances to port 8989.
    Affected if Port 8989 is reachable from untrusted networks or is explicitly allowed through the firewall to external clients.
  4. Inspect .NET Remoting configuration
    Examine the Sentinel application configuration files (typically in the installation directory) for .NET Remoting HTTP channel settings on port 8989. Look for <channel> elements or remoting-related configuration.
    Affected if The .NET Remoting HTTP channel on port 8989 is configured and enabled in the application.

You are affected if Sentinel version is 10.5.x or 11.x below 11.6.0 AND port 8989 is both listening and network-accessible, enabling the unauthenticated RCE pathway.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict or block network access to port 8989 via firewall rules or network segmentation if exposed, and apply vendor patches (version 11.6.0 or later) when available.

Recommended fix Moderate confidence

Sentinel version 11.6.0 or later

  1. Verify current Sentinel installation version by checking the application or system information
  2. Download Sentinel version 11.6.0 or later from the official Spacelabs Healthcare support portal
  3. Review Spacelabs Healthcare release notes for version 11.6.0 to understand changes and prerequisites
  4. Create a complete backup of the current Sentinel installation, including configuration files and databases
  5. If the system is used in a production healthcare environment, coordinate with IT and clinical staff for a maintenance window
  6. Stop all Sentinel services and IIS before applying the upgrade
  7. Install Sentinel version 11.6.0 or later following the vendor's upgrade documentation
  8. Verify that port 8989 (the .NET Remoting HTTP channel) remains disabled or internal-only if still present in the new version
Caveat As medical device software, upgrades may require validation testing and regulatory compliance review in healthcare environments; coordinate with clinical engineering before deployment

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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