Is CVE-2026-92237 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92237 being exploited in the wild.

How severe is CVE-2026-92237?

Medium severity, with a CVSS score of 6.5, published 15 September 2026.

Which products and versions are affected?

Devolutions PowerShell Universal 2026.2.5 and earlier.

Is there a fix for CVE-2026-92237?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-92237 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-92237?

Check whether you run Devolutions PowerShell Universal at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-92237: Devolutions PowerShell Universal sensitive information disclosure in query logs

CVE-2026-92237 · Severity: medium · CVSS 6.5 · Published 2026-09-15

Devolutions PowerShell Universal is an IT automation platform used to streamline remote management tasks with dashboards and APIs. A flaw in the slow query logging feature causes sensitive data—including application tokens, encryption keys, and stored credentials—to be written to system logs in plaintext. An authenticated user with permission to read logs can extract these secrets, potentially leading to account takeover and unauthorized access to protected systems.

Technologies: Devolutions PowerShell Universal. Vendors: Devolutions.

Quick answers

Is CVE-2026-92237 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92237 being exploited in the wild.
How severe is CVE-2026-92237?: Medium severity, with a CVSS score of 6.5, published 15 September 2026.
Which products and versions are affected?: Devolutions PowerShell Universal 2026.2.5 and earlier.
Is there a fix for CVE-2026-92237?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-92237 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-92237?: Check whether you run Devolutions PowerShell Universal at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an insertion of sensitive information into log files (CWE-532) affecting the slow query logging feature in PowerShell Universal when running on Microsoft SQL Server backends. The root cause is that SQL parameter values containing secrets are logged without sanitization. An authenticated attacker with log read permissions can extract application tokens, data protection key material, and credentials from the system logs. The vulnerability requires authenticated access and log read permissions to exploit. This affects PowerShell Universal versions 2026.2.5 and earlier running on SQL Server.

Affected products

Devolutions PowerShell Universal 2026.2.5 and earlier

Timeline

2026-09-15: disclosed

References

https://devolutions.net/security/advisories/DEVO-2026-0031/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.