CVE-2026-53513

CRITICALPre-NVD 9.69.6
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.6 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
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 9.6Exploit: 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. Prior to 1.6.11, the @better-auth/sso plugin's POST /sso/register and POST /sso/update-provider endpoints accept attacker-controlled oidcConfig.userInfoEndpoint, tokenEndpoint, and jwksEndpoint URLs when skipDiscovery: true is set, store them on the ssoProvider row without origin validation, and fetch them during OIDC callback, allowing non-blind server-side request forgery and possible account linking when trustEmailVerified: true is configured. This issue is fixed in version 1.6.11.

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

Published

July 7, 2026

Last Modified

July 15, 2026

Advisory Details (4)

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

@better-auth/sso: Server-side request forgery via unvalidated OIDC endpoints on provider registration · Advisory · better-auth/better-auth · GitHub

https://github.com/better-auth/better-auth/security/advisories/GHSA-5rr4-8452-hf4v
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_pr

fix(sso): validate user-supplied OIDC endpoint URLs at registration and update

Fix merged in better-auth/better-auth PR #9574 on 2026-05-12 — awaiting tagged release

https://github.com/better-auth/better-auth/pull/9574
github_commit

commit 37f60cb176cb (better-auth/better-auth)

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

https://github.com/better-auth/better-auth/commit/37f60cb176cb53147da7dfd5ec15afa5b486e81e

Vendor Advisories for CVE-2026-53513(1)

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

Weakness Classification(4)

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

Data Freshness Timeline

(refreshed 38× in last 7d / 45× 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 22:20 UTCEG score recompute
  2. 2026-07-15 17:58 UTCEG score recompute
  3. 2026-07-15 13:35 UTCEG score recompute
  4. 2026-07-15 09:10 UTCEG score recompute
  5. 2026-07-15 04:46 UTCEG score recompute
  6. 2026-07-15 00:19 UTCEG score recompute
  7. 2026-07-14 19:56 UTCEG score recompute
  8. 2026-07-14 15:33 UTCEG score recompute
  9. 2026-07-14 11:10 UTCEG score recompute
  10. 2026-07-14 06:45 UTCEG score recompute
  11. 2026-07-14 02:22 UTCEG score recompute
  12. 2026-07-13 21:59 UTCEG score recompute
  13. 2026-07-13 17:36 UTCEG score recompute
  14. 2026-07-13 13:13 UTCEG score recompute
  15. 2026-07-13 08:50 UTCEG score recompute
  16. 2026-07-13 04:26 UTCEG score recompute
  17. 2026-07-13 00:02 UTCEG score recompute
  18. 2026-07-12 19:37 UTCEG score recompute
  19. 2026-07-12 15:14 UTCEG score recompute
  20. 2026-07-12 10:51 UTCEG score recompute
  21. 2026-07-12 06:29 UTCEG score recompute
  22. 2026-07-12 02:06 UTCEG score recompute
  23. 2026-07-11 21:42 UTCEG score recompute
  24. 2026-07-11 17:19 UTCEG score recompute
  25. 2026-07-11 12:56 UTCEG score recompute
Show 20 more
  1. 2026-07-11 08:33 UTCEG score recompute
  2. 2026-07-11 04:10 UTCEG score recompute
  3. 2026-07-10 23:46 UTCEG score recompute
  4. 2026-07-10 19:23 UTCEG score recompute
  5. 2026-07-10 15:00 UTCEG score recompute
  6. 2026-07-10 10:37 UTCEG score recompute
  7. 2026-07-10 06:10 UTCEG score recompute
  8. 2026-07-10 01:46 UTCEG score recompute
  9. 2026-07-09 21:23 UTCEG score recompute
  10. 2026-07-09 17:01 UTCEG score recompute
  11. 2026-07-09 12:37 UTCEG score recompute
  12. 2026-07-09 08:15 UTCEG score recompute
  13. 2026-07-09 03:52 UTCEG score recompute
  14. 2026-07-08 23:29 UTCEG score recompute
  15. 2026-07-08 19:07 UTCEG score recompute
  16. 2026-07-08 14:44 UTCEG score recompute
  17. 2026-07-08 10:22 UTCEG score recompute
  18. 2026-07-08 05:58 UTCEG score recompute
  19. 2026-07-08 01:35 UTCEG score recompute
  20. 2026-07-07 21:13 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-53513?
CVE-2026-53513 is a critical vulnerability published on July 7, 2026. Better Auth is an authentication and authorization library for TypeScript. Prior to 1.6.11, the @better-auth/sso plugin's POST /sso/register and POST /sso/update-provider endpoints accept attacker-controlled oidcConfig.userInfoEndpoint, tokenEndpoint, and jwksEndpoint URLs when skipDiscovery: true…
When was CVE-2026-53513 disclosed?
CVE-2026-53513 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-53513?
CVE-2026-53513 has a CVSS v3 base score of 9.6 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-53513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53513, 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-53513

Explore →

Is Your Infrastructure Affected by CVE-2026-53513?

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

Start Free Scan →Browse All CVEs