# CVE-2026-114485: Insufficient protection of sensitive information in the user list endpoint in Devolutions Server 2026.3.10.0 and earlier allows an authentic


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-9v47-334m-r224

## What is CVE-2026-114485?

CVE-2026-114485 is a vulnerability in Devolutions Server, published on 22 Oct 2026. 

### Official description

Insufficient protection of sensitive information in the user list endpoint in Devolutions Server 
2026.3.10.0 and earlier allows an authenticated attacker with delegated user view permissions to obtain the MFA secrets of all users via the user list API response.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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


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

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

## Is CVE-2026-114485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114485 is a vulnerability in Devolutions Server, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114485 in the wild and no public exploit code.

Affected product: Devolutions Server. 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-114485/ (Markdown: https://insights.sbomify.com/CVE-2026-114485/index.md)
```

## Sources

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

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