# CVE-2026-93330: Security feature bypass in Server

> Users with PAM edit permissions can bypass Devolutions Gateway host rulesets due to improper rule enforcement in the Active Directory provider.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-r6vr-3f2x-8mx5

## What is CVE-2026-93330?

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

### Official description

Improper rule enforcement in the PAM Active Directory provider in Devolutions Server 2026.3.5 allows a user with PAM edit permissions to bypass the Devolutions Gateway host ruleset.

Weakness: CWE-696 (Incorrect Behavior Order)

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


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

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

## Is CVE-2026-93330 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93330 is a medium-severity vulnerability in Devolutions Server, published on 29 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-93330 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-93330/ (Markdown: https://insights.sbomify.com/CVE-2026-93330/index.md)
```

## Sources

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

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