dbcve.org
Nuance Powerscribe 360Application · Microsoft

CVE-2026-26142

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-09
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
Deserialization of untrusted data in Nuance PowerScribe allows an unauthorized attacker to execute code over a network.

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 · moderate confidence

This is a critical deserialization vulnerability in Nuance PowerScribe (radiology reporting software) where the application deserializes data from untrusted sources without proper validation. This unsafe deserialization allows an unauthenticated remote attacker to execute arbitrary code on the affected system, likely through malicious serialized objects sent over the network.

MitigationApply vendor-supplied patches immediately; restrict network exposure of the affected system and implement strict inbound access controls; if patching is delayed, consider network segmentation to limit attack surface.

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
Nuance Powerscribe 360Application
Affected:= 4.0.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 4.0.8= 4.0.9
Nuance Powerscribe OneApplication
Affected:= 2019.1= 2019.2= 2019.3= 2019.4= 2019.5= 2019.6= 2019.7= 2019.8= 2019.9= 2019.10= 2023.1

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. Identify if PowerScribe 360 is installed
    Check for PowerScribe 360 installation directories (typically C:\Program Files\Nuance\PowerScribe 360 or C:\Program Files (x86)\Nuance\PowerScribe 360) and look for version information in installation manifests or the application's About/Version dialog.
    Affected if PowerScribe 360 version is 4.0.0 through 4.0.9 inclusive
  2. Identify if PowerScribe One is installed
    Check for PowerScribe One installation directories (typically under C:\Program Files\Nuance\PowerScribe One or C:\Program Files (x86)\Nuance\PowerScribe One) and locate version information in version.xml, about dialog, or registry uninstall keys.
    Affected if PowerScribe One version is 2019.1 through 2019.10 or 2023.1
  3. Check for network-exposed PowerScribe services
    Use netstat or PowerShell Get-NetTCPConnection to enumerate listening ports on the server. PowerScribe typically uses specific ports for its reporting services (consult system documentation for your version). Identify any ports bound to 0.0.0.0 or external interfaces.
    Affected if PowerScribe services are listening on network-accessible interfaces (0.0.0.0 or external IP) rather than only localhost (127.0.0.1)
  4. Verify deserialization endpoints are accessible
    Review IIS or embedded web server configuration files in the PowerScribe installation directory for exposed .asmx, .soap, or similar endpoints that handle serialized data. Check web.config for serialization settings.
    Affected if Deserialization endpoints are exposed without authentication or network restrictions

You are affected if PowerScribe 360 version 4.0.0-4.0.9 or PowerScribe One version 2019.1-2019.10/2023.1 is installed and the service is network-accessible, allowing unauthenticated deserialization attacks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches immediately; restrict network exposure of the affected system and implement strict inbound access controls; if patching is delayed, consider network segmentation to limit attack surface.

Fix this in Nuance Powerscribe 360 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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