Quick answers
- Is CVE-2026-45337 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45337 being exploited in the wild.
- How severe is CVE-2026-45337?
- High severity, with a CVSS score of 7.6, published 15 July 2026.
- Which products and versions are affected?
- better-auth (npm) >= 1.6.0, < 1.6.11, SEMVER:introduced=1.6.0,fixed=1.6.11.
- Is there a fix for CVE-2026-45337?
- Yes. better-auth (npm): upgrade to 1.6.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45337 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-45337?
- Check whether you run better-auth (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- better-auth (npm): upgrade to 1.6.11 or later
npm install better-auth@1.6.11
Technical details
An authorization bypass exists in the Better Auth deviceAuthorization plugin due to improper ownership validation. The 'GET /device' endpoint fails to claim the pending device code row for the authenticated session, and the 'POST /device/approve' and 'POST /device/deny' endpoints short-circuit their ownership checks when the 'userId' field is NULL. An authenticated attacker who obtains a valid 'user_code' can exploit this to bind their own account to the victim's polling device. The vulnerability is fixed in version 1.6.11 by ensuring 'GET /device' claims the row and enforcing strict session-to-owner equality in subsequent requests.
Affected products
- better-auth better-auth >= 1.6.0, < 1.6.11
Identifiers
- CVE-2026-45337
- GHSA-cq3f-vc6p-68fh
Timeline
- 2026-05-12: patched: Fix merged in PR #9573 and released in v1.6.11
- 2026-05-31: advisory: GitHub Security Advisory GHSA-cq3f-vc6p-68fh published
- 2026-07-15: disclosed: CVE-2026-45337 published to NVD