CVE-2026-67333 json
better-auth before 1.6.13 Stored XSS via javascript redirect_uri
published 5mo ago modified last mo. also EUVD-2026-51810 , GHSA-86j7-9j95-vpqj
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
better-auth before 1.6.13 (and pre-release builds 1.7.0-beta.0 through 1.7.0-beta.3) fail to validate the scheme of redirect_uris registered via the deprecated oidc-provider plugin and the mcp plugin (which wraps the same provider). An attacker can register an OAuth client with a javascript: redirect_uri, which the authorization server later returns unchanged in the consent response. If the deployment's consent page navigates the browser to the returned redirectURI (e.g. assigning it to window.location.href), the attacker's JavaScript executes in the authorization-server origin, exposing the victim's session and enabling account takeover.
Patch / fix
- npm better-auth 1.6.13, 1.7.0-beta.4
- better-auth better-auth 1.6.13, 1.7.0-beta.4
Is CVE-2026-67333 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
- yes
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N |
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N |
| CNA | 4.0 | 5.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | better-auth | <1.6.13 >=1.7.0-beta.0, <1.7.0-beta.4 |
1.6.13 1.7.0-beta.4 |
Affected products
- better-auth better-auth
Classification
References
-
github.com
/better-auth/better-auth/security/advisories/GHSA-86j7-9j95-vpqj
vendor-advisory, web, advisory
-
vulncheck.com
/advisories/better-auth-before-stored-xss-via-javascript-redirect-uri
third-party-advisory
-
github.com
/better-auth/better-auth
package
-
github.com
/better-auth/better-auth/releases/tag/v1.6.13
web
-
github.com
/better-auth/better-auth/releases/tag/v1.7.0-beta.4
web
Sources
- CVE List CVE-2026-67333
- GitHub Advisory GHSA-86j7-9j95-vpqj
- NVD CVE-2026-67333
- Maintainer advisory GHSA-86j7-9j95-vpqj
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.