# CVE-2026-9226: Auth bypass in Server

> Remote attackers can take over user accounts by replaying captured login tokens exposed in redirect URLs during Azure AD external login flows.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-jfrq-j4wj-3h93

## What is CVE-2026-9226?

CVE-2026-9226 is a medium-severity authentication bypass vulnerability in Devolutions Server, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Authentication bypass in the Azure AD external login flow in Devolutions Server 2026.3.7.0 and earlier allows a remote attacker to take over a user's account via replay of a captured login-session token exposed in a redirect URL.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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


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

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

## Is CVE-2026-9226 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9226 is a medium-severity authentication bypass vulnerability in Devolutions Server, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9226 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-9226/ (Markdown: https://insights.sbomify.com/CVE-2026-9226/index.md)
```

## Sources

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

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