# CVE-2026-92237: Information disclosure in PowerShell Universal

> Authenticated users with log access can retrieve sensitive credentials and keys from SQL Server-backed instances via slow query logs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-wchh-mww7-897w

## What is CVE-2026-92237?

CVE-2026-92237 is a medium-severity vulnerability in Devolutions PowerShell Universal, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insertion of sensitive information into log file in the slow query logging feature in Devolutions PowerShell Universal 2026.2.5 and earlier allows an authenticated user with log read permission to obtain application tokens, data protection key material and other stored credentials via SQL parameter values written to the system log on instances backed by Microsoft SQL Server.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-92237?


## How do I fix CVE-2026-92237?

No fix has been published for CVE-2026-92237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92237 being exploited?

There is no known exploitation of CVE-2026-92237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92237 and fix it if it is affected.

What it is: CVE-2026-92237 is a medium-severity vulnerability in Devolutions PowerShell Universal, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92237 in the wild and no public exploit code.

Affected product: Devolutions PowerShell Universal. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92237/ (Markdown: https://insights.sbomify.com/CVE-2026-92237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92237
- OSV: https://osv.dev/vulnerability/CVE-2026-92237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92237/
Summaries are generated and may contain mistakes; the official description above is the record.