Security readout for executives and security teams
Plain-English summary
A network attacker could compromise affected Nuance PowerScribe systems without credentials or user interaction. Successful exploitation could allow data theft, unauthorized changes, and service disruption. The vulnerability is critical because exploitation is rated low complexity and could fully affect confidentiality, integrity, and availability.
Executive priority
Treat this as an immediate remediation priority for confirmed affected deployments, especially attacker-reachable systems. Assign ownership, establish an expedited maintenance window, and require evidence that vendor guidance was applied. Escalate compensating network restrictions where remediation cannot be completed promptly.
Technical view
CVE-2026-26142 is a CWE-502 deserialization flaw that permits remote code execution through untrusted data. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges, and no user interaction. The supplied evidence does not identify the vulnerable endpoint, protocol, or code-execution context.
Likely exposure
Potential exposure includes Nuance PowerScribe 360 versions 4.0 through 4.0.9 and PowerScribe One versions 2019.1 through 2019.10. Risk is greatest where an affected service is reachable from untrusted networks. The bundle provides no CPEs or deployment-specific exposure details.
Exploitation context
The CVSS assessment indicates unauthenticated remote exploitation with low complexity and no user interaction. However, the source bundle reports no CISA KEV listing and provides no evidence of active exploitation or public exploit availability. Treat exploit status as unconfirmed.
Researcher notes
The record establishes unsafe deserialization and remote code execution, but lacks endpoint, protocol, component, execution-privilege, and detection details. No CPEs are supplied. Researchers should avoid inferring affected releases beyond the enumerated versions and should consult Microsoft for authoritative remediation and technical updates.
Mitigation direction
- Review the Microsoft advisory for the vendor-supported remediation applicable to each installed version.
- Apply the vendor-supported update or mitigation after appropriate operational testing.
- Restrict affected services to trusted networks and authorized systems wherever operationally feasible.
- Prioritize backups and recovery readiness before remediation changes.
Validation and detection
- Inventory all PowerScribe 360 and PowerScribe One deployments and record exact versions.
- Confirm whether affected services are reachable from untrusted or unnecessary network segments.
- Verify the Microsoft-recommended remediation is installed on every affected instance.
- Review available service, host, and network telemetry for unexplained access or execution anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-26142 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C3.95.9microsoftVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Nuance PowerScribe Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.