# CVE-2026-45337: Better Auth: Device authorization approve and deny accept any authenticated session while the user code is pending

> An authenticated attacker can hijack pending device authorization flows by binding them to their own account or denying legitimate requests.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-cq3f-vc6p-68fh

## What is CVE-2026-45337?

CVE-2026-45337 is a high-severity authentication bypass vulnerability in better-auth, published on 15 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Better Auth is an authentication and authorization library for TypeScript. From 1.6.0 until 1.6.11, the deviceAuthorization plugin treats any authenticated session as the owner of any pending device code because GET /device does not claim the row and POST /device/approve and POST /device/deny short-circuit when userId is unset, allowing an authenticated attacker who learns a valid user_code to bind the polling device to the attacker's account or deny the legitimate flow. This issue is fixed in version 1.6.11.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-285 (Improper Authorization)

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

2 open source packages ship an affected version, including better-auth. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `better-auth` | npm | From 1.6.0 | 1.6.11 |
| `better-auth` | npm | From 1.6.0 | 1.6.11 |

Products: Better-Auth Better Auth.

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

Upgrade better-auth to 1.6.11 or later.

## Is CVE-2026-45337 being exploited?

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

## Other vulnerabilities in better-auth

- [CVE-2026-53512](https://insights.sbomify.com/CVE-2026-53512/): Better Auth: OAuth refresh-token replay via missing client authentication on oidc-provider and mcp plugins (critical 9.1)
- [CVE-2026-53516](https://insights.sbomify.com/CVE-2026-53516/): Better Auth: Account takeover via OAuth auto-link to unverified pre-registered email (high 8.3)
- [CVE-2024-56734](https://insights.sbomify.com/CVE-2024-56734/): Better Auth has an Open Redirect Vulnerability in Verify Email Endpoint (high 7.9)
- [CVE-2026-53514](https://insights.sbomify.com/CVE-2026-53514/): Better Auth: Unauthorized invitation acceptance via unverified email match in organization plugin (high 7.7)
- [CVE-2025-27143](https://insights.sbomify.com/CVE-2025-27143/): Beter Auth has an Open Redirect via Scheme-Less Callback Parameter (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45337 is a high-severity authentication bypass vulnerability in better-auth, published on 15 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-45337 in the wild and no public exploit code.

Affected packages and fixed versions:
- better-auth (npm): affected from 1.6.0; fixed in 1.6.11
- better-auth (npm): affected from 1.6.0; fixed in 1.6.11

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-45337/ (Markdown: https://insights.sbomify.com/CVE-2026-45337/index.md)
```

## Sources

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

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