CVE-2026-67330

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreHIGH confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-01. a secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 0

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

@better-auth/scim (a better-auth plugin) versions >= 1.4.0-beta.27 through <= 1.6.21 and >= 1.7.0-beta.0 through <= 1.7.0-beta.9 contain an authorization bypass. SCIM token issuance did not reject provider IDs already used by existing SSO, SAML, OIDC, generic OAuth, or social account providers, and the same logical provider ID was used for both SCIM provider configuration and account ownership. An authenticated user could mint a SCIM token whose provider ID collided with an existing provider namespace, causing SCIM user routes to resolve account rows the token never provisioned. This allowed listing, reading, updating (including rewriting global profile/email fields without uniqueness checks), and deleting global user accounts and sessions, resulting in account takeover and unauthorized deprovisioning. Fixed in 1.6.22 and 1.7.0-beta.10 (1.7.0-rc.0).

CVSS v3
9.9
EG Score
9.9(high)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 3, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available. Sources: github.
generic

better-auth SCIM 1.4.0-beta.27 through 1.6.21 Account Takeover via Provider-ID Collision | Advisories | VulnCheck

https://www.vulncheck.com/advisories/better-auth-scim-beta-27-through-account-takeover-via-provider-id-collision
github Patch Available

@better-auth/scim: account takeover and stale access via SCIM provider-id collision · Advisory · better-auth/better-auth · GitHub

https://github.com/better-auth/better-auth/security/advisories/GHSA-rjg6-39jm-rgg4

Vendor Advisories for CVE-2026-67330(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 53× in last 7d / 153× 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.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-08-20 16:12 UTCGHSA enrichment
  2. 2026-08-20 12:08 UTCGHSA enrichment
  3. 2026-08-20 07:59 UTCGHSA enrichment
  4. 2026-08-20 03:55 UTCGHSA enrichment
  5. 2026-08-19 23:51 UTCGHSA enrichment
  6. 2026-08-19 19:46 UTCEG score recompute
  7. 2026-08-19 19:46 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 15:41 UTCGHSA enrichment
  10. 2026-08-19 11:37 UTCGHSA enrichment
  11. 2026-08-19 07:30 UTCGHSA enrichment
  12. 2026-08-19 03:23 UTCGHSA enrichment
  13. 2026-08-18 22:26 UTCGHSA enrichment
  14. 2026-08-18 18:22 UTCEG score recompute
  15. 2026-08-18 18:22 UTCGHSA enrichment
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-18 12:51 UTCGHSA enrichment
  18. 2026-08-18 08:41 UTCGHSA enrichment
  19. 2026-08-18 04:25 UTCGHSA enrichment
  20. 2026-08-18 00:21 UTCGHSA enrichment
  21. 2026-08-17 20:00 UTCGHSA enrichment
  22. 2026-08-17 15:54 UTCEG score recompute
  23. 2026-08-17 15:54 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 11:49 UTCGHSA enrichment
Show 75 more
  1. 2026-08-17 07:45 UTCGHSA enrichment
  2. 2026-08-17 03:41 UTCGHSA enrichment
  3. 2026-08-16 23:37 UTCGHSA enrichment
  4. 2026-08-16 19:33 UTCGHSA enrichment
  5. 2026-08-16 15:28 UTCEG score recompute
  6. 2026-08-16 15:28 UTCGHSA enrichment
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 11:24 UTCGHSA enrichment
  9. 2026-08-16 07:20 UTCGHSA enrichment
  10. 2026-08-16 03:16 UTCEG score recompute
  11. 2026-08-16 03:16 UTCGHSA enrichment
  12. 2026-08-15 23:12 UTCGHSA enrichment
  13. 2026-08-15 19:08 UTCGHSA enrichment
  14. 2026-08-15 15:04 UTCGHSA enrichment
  15. 2026-08-15 11:00 UTCGHSA enrichment
  16. 2026-08-15 06:56 UTCGHSA enrichment
  17. 2026-08-15 02:26 UTCEG score recompute
  18. 2026-08-15 02:26 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 22:22 UTCGHSA enrichment
  21. 2026-08-14 18:18 UTCGHSA enrichment
  22. 2026-08-14 14:14 UTCGHSA enrichment
  23. 2026-08-14 10:10 UTCGHSA enrichment
  24. 2026-08-14 06:06 UTCGHSA enrichment
  25. 2026-08-14 02:01 UTCEG score recompute
  26. 2026-08-14 02:01 UTCGHSA enrichment
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 21:57 UTCGHSA enrichment
  29. 2026-08-13 17:53 UTCGHSA enrichment
  30. 2026-08-13 13:49 UTCGHSA enrichment
  31. 2026-08-13 09:45 UTCGHSA enrichment
  32. 2026-08-13 05:41 UTCGHSA enrichment
  33. 2026-08-13 01:36 UTCGHSA enrichment
  34. 2026-08-12 21:32 UTCGHSA enrichment
  35. 2026-08-12 17:28 UTCEG score recompute
  36. 2026-08-12 17:28 UTCGHSA enrichment
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-12 13:24 UTCGHSA enrichment
  39. 2026-08-12 09:19 UTCGHSA enrichment
  40. 2026-08-12 05:15 UTCGHSA enrichment
  41. 2026-08-12 01:10 UTCGHSA enrichment
  42. 2026-08-11 21:06 UTCGHSA enrichment
  43. 2026-08-11 17:02 UTCEG score recompute
  44. 2026-08-11 17:02 UTCGHSA enrichment
  45. 2026-08-11 12:58 UTCGHSA enrichment
  46. 2026-08-11 08:54 UTCGHSA enrichment
  47. 2026-08-11 04:50 UTCGHSA enrichment
  48. 2026-08-11 00:46 UTCEG score recompute
  49. 2026-08-11 00:46 UTCGHSA enrichment
  50. 2026-08-11 00:00 UTCEPSS rescore
  51. 2026-08-10 20:42 UTCGHSA enrichment
  52. 2026-08-10 16:37 UTCGHSA enrichment
  53. 2026-08-10 12:31 UTCGHSA enrichment
  54. 2026-08-10 08:27 UTCGHSA enrichment
  55. 2026-08-10 04:23 UTCGHSA enrichment
  56. 2026-08-10 00:19 UTCGHSA enrichment
  57. 2026-08-09 20:15 UTCGHSA enrichment
  58. 2026-08-09 16:11 UTCEG score recompute
  59. 2026-08-09 16:11 UTCGHSA enrichment
  60. 2026-08-09 13:47 UTCEPSS rescore
  61. 2026-08-09 12:07 UTCGHSA enrichment
  62. 2026-08-09 08:02 UTCGHSA enrichment
  63. 2026-08-09 03:58 UTCGHSA enrichment
  64. 2026-08-08 23:54 UTCGHSA enrichment
  65. 2026-08-08 19:50 UTCEG score recompute
  66. 2026-08-08 19:50 UTCGHSA enrichment
  67. 2026-08-08 16:37 UTCEPSS rescore
  68. 2026-08-08 15:45 UTCGHSA enrichment
  69. 2026-08-08 11:41 UTCGHSA enrichment
  70. 2026-08-08 07:37 UTCGHSA enrichment
  71. 2026-08-08 03:33 UTCGHSA enrichment
  72. 2026-08-07 23:29 UTCGHSA enrichment
  73. 2026-08-07 19:25 UTCEG score recompute
  74. 2026-08-07 19:25 UTCGHSA enrichment
  75. 2026-08-07 15:20 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67330?
CVE-2026-67330 is a critical vulnerability published on August 1, 2026. @better-auth/scim (a better-auth plugin) versions >= 1.4.0-beta.27 through <= 1.6.21 and >= 1.7.0-beta.0 through <= 1.7.0-beta.9 contain an authorization bypass. SCIM token issuance did not reject provider IDs already used by existing SSO, SAML, OIDC, generic OAuth, or social account providers, and…
When was CVE-2026-67330 disclosed?
CVE-2026-67330 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67330 actively exploited?
CVE-2026-67330 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.6% of all scored CVEs.
What is the CVSS score of CVE-2026-67330?
CVE-2026-67330 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-67330?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67330, 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-67330

Explore →

Is Your Infrastructure Affected by CVE-2026-67330?

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

Start Free Scan →Browse All CVEs