CVE-2026-53518 json
Better Auth OAuth Provider: Race Condition in Authorization Code Exchange Enables Multi-Use Code Redemption
published 5mo ago modified last mo. also EUVD-2026-44734 , GHSA-7w99-5wm4-3g79
- cvss
- 8.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 35%
- public exploits
- 0
- none known
Summary
Better Auth is an authentication and authorization library for TypeScript. From 1.6.0 until 1.6.11, the @better-auth/oauth-provider POST /oauth2/token endpoint for the authorization_code grant redeems a single-use authorization code through a non-atomic find-then-delete sequence, allowing two concurrent requests to pass the read step and mint independent access tokens, refresh tokens, and ID tokens; legacy /oauth2/token and /mcp/token paths in oidc-provider and mcp plugins share the same primitive. This issue is fixed in version 1.6.11.
Patch / fix
- npm @better-auth/oauth-provider 1.6.11
- npm better-auth 1.6.11
- better-auth better-auth/oauth-provider 1.6.11
- better-auth better_auth 1.6.11
Is CVE-2026-53518 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.6 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| CNA | 4.0 | 7.6 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @better-auth/oauth-provider | >=1.6.0, <1.6.11 |
1.6.11 |
| npm | better-auth | <1.6.11 |
1.6.11 |
Affected products
- better-auth better-auth
Classification
References
-
github.com
/better-auth/better-auth/commit/b4bc65a007784b2eb0efb459e5fa6fd8055d3ec9
web, patch
-
github.com
/better-auth/better-auth/security/advisories/GHSA-7w99-5wm4-3g79
web, mitigation, vendor-advisory, advisory
-
github.com
/better-auth/better-auth/releases/tag/v1.6.11
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-53518
advisory
-
github.com
/better-auth/better-auth
package
Sources
- CVE List CVE-2026-53518
- GitHub Advisory GHSA-7w99-5wm4-3g79
- NVD CVE-2026-53518
- Maintainer advisory GHSA-7w99-5wm4-3g79
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of better-auth/better-auth published their own advisory on GitHub. Reviewed sources take precedence over it.