Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-q84f-53jg-9ppm

better-auth: Device login approval does not show the requesting client or permissions

CVSS 8.5 HighEPSS 0.0028 · 20th percentile

Published by the GitHub Advisory Database at 27 Oct 2026, 14:49 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
better-authnpm>=1.3.8-beta.3, <1.7.0-rc.31.7.0-rc.3
Identifiers
GHSA-q84f-53jg-9ppm · CVE-2026-109346
Weakness (CWE)
CWE-451
Tags
Published
27 Oct 2026
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Better-auth versions from 1.3.8-beta.3 up to but not including 1.7.0-rc.3 are affected when the deviceAuthorization() plugin is enabled. The approval page does not show which client is requesting access or which permissions it asks for. An attacker who can start a device request and convince a signed-in user to approve it could obtain a session token for that user and act on their account. Upgrade to better-auth 1.7.0 or later; no 1.6 release contains the fix. If you cannot upgrade, disable the plugin or build a custom approval page that shows the client and requested permissions.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.5 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0028, the 20th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.