CVE-2026-53517

HIGHPre-NVD 8.18.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Better Auth is an authentication and authorization library for TypeScript. From 1.4.8-beta.7 until 1.6.11, the @better-auth/oauth-provider POST /oauth2/token endpoint on the refresh_token grant performs a non-atomic read, validate, revoke, and mint sequence on the oauthRefreshToken row, allowing concurrent requests with the same parent refresh token to pass the revoked check and create forked refresh-token families; the vulnerable range also includes embedded better-auth plugin versions before 1.6.0. This issue is fixed in version 1.6.11.

CVSS v3
8.1
EG Score
8.1(low)
EPSS
—
KEV
Not listed

Published

July 7, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

@better-auth/oauth-provider: OAuth refresh-token rotation forks the token family on concurrent redemption · Advisory · better-auth/better-auth · GitHub

https://github.com/better-auth/better-auth/security/advisories/GHSA-392p-2q2v-4372
github_release Patch Available

v1.6.11

Patch available: better-auth/better-auth v1.6.11

https://github.com/better-auth/better-auth/releases/tag/v1.6.11
github_commit

commit c6918ecc9e3a (better-auth/better-auth)

Fix landed in better-auth/better-auth commit c6918ecc9e3a — awaiting tagged release

https://github.com/better-auth/better-auth/commit/c6918ecc9e3a75892169415d7f6c95b591b6a52d

Vendor Advisories for CVE-2026-53517(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 23:14 UTCEG score recompute
  2. 2026-07-15 11:49 UTCEG score recompute
  3. 2026-07-15 00:24 UTCEG score recompute
  4. 2026-07-14 13:00 UTCEG score recompute
  5. 2026-07-14 01:36 UTCEG score recompute
  6. 2026-07-13 14:11 UTCEG score recompute
  7. 2026-07-13 02:45 UTCEG score recompute
  8. 2026-07-12 15:20 UTCEG score recompute
  9. 2026-07-12 03:55 UTCEG score recompute
  10. 2026-07-11 16:30 UTCEG score recompute
  11. 2026-07-11 05:06 UTCEG score recompute
  12. 2026-07-10 17:42 UTCEG score recompute
  13. 2026-07-10 06:18 UTCEG score recompute
  14. 2026-07-09 18:53 UTCEG score recompute
  15. 2026-07-09 07:29 UTCEG score recompute
  16. 2026-07-08 20:04 UTCEG score recompute
  17. 2026-07-08 08:39 UTCEG score recompute
  18. 2026-07-07 21:13 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-53517?
CVE-2026-53517 is a high vulnerability published on July 7, 2026. Better Auth is an authentication and authorization library for TypeScript. From 1.4.8-beta.7 until 1.6.11, the @better-auth/oauth-provider POST /oauth2/token endpoint on the refresh_token grant performs a non-atomic read, validate, revoke, and mint sequence on the oauthRefreshToken row, allowing…
When was CVE-2026-53517 disclosed?
CVE-2026-53517 was first published in the National Vulnerability Database on July 7, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-53517?
CVE-2026-53517 has a CVSS v3 base score of 8.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-53517?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53517, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53517

Explore →

Is Your Infrastructure Affected by CVE-2026-53517?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs