CVE-2026-67331

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. the CNA's CVSS baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this weekElevated
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: Elevated riskExposed: 0

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

better-auth SCIM versions from 1.5.0 before 1.7.0-beta.4 fail to bind non-organization SCIM providers to their creator by default, allowing authenticated users to manage other users' providers. Attackers can regenerate SCIM bearer tokens, invalidate legitimate tokens, and authenticate to SCIM API routes with the attacker-controlled token.

CVSS v3
8.3
EG Score
8.3(high)
EG Risk
53(Track)
EG Risk 53/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
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 1, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

better-auth SCIM 1.5.0 before 1.7.0-beta.4 Authorization Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/better-auth-scim-before-beta-4-authorization-bypass
github Patch Available🟡 PoC Available

@better-auth/scim: on single tenant use cases authenticated user can regenerate SCIM provider token · Advisory · better-auth/better-auth · GitHub

https://github.com/better-auth/better-auth/security/advisories/GHSA-j8v8-g9cx-5qf4

Vendor Advisories for CVE-2026-67331(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@better-auth/scim—1.7.0-beta.4—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 82× 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-08-21 05:45 UTCEG score recompute
  2. 2026-08-21 05:45 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 16:50 UTCGHSA enrichment
  5. 2026-08-20 03:46 UTCEG score recompute
  6. 2026-08-20 03:46 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 14:49 UTCGHSA enrichment
  9. 2026-08-19 01:52 UTCEG score recompute
  10. 2026-08-19 01:52 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 12:51 UTCGHSA enrichment
  13. 2026-08-17 23:33 UTCEG score recompute
  14. 2026-08-17 23:33 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 10:37 UTCGHSA enrichment
  17. 2026-08-16 21:42 UTCEG score recompute
  18. 2026-08-16 21:42 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 08:46 UTCEG score recompute
  21. 2026-08-16 08:46 UTCGHSA enrichment
  22. 2026-08-15 19:51 UTCGHSA enrichment
  23. 2026-08-15 06:56 UTCEG score recompute
  24. 2026-08-15 06:56 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 57 more
  1. 2026-08-14 17:11 UTCEG score recompute
  2. 2026-08-14 17:11 UTCGHSA enrichment
  3. 2026-08-14 12:47 UTCGHSA enrichment
  4. 2026-08-13 23:52 UTCEG score recompute
  5. 2026-08-13 23:52 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 10:56 UTCGHSA enrichment
  8. 2026-08-12 22:01 UTCEG score recompute
  9. 2026-08-12 22:01 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 09:06 UTCGHSA enrichment
  12. 2026-08-11 20:11 UTCEG score recompute
  13. 2026-08-11 20:11 UTCGHSA enrichment
  14. 2026-08-11 07:16 UTCEG score recompute
  15. 2026-08-11 07:16 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 18:21 UTCGHSA enrichment
  18. 2026-08-10 05:25 UTCGHSA enrichment
  19. 2026-08-09 16:30 UTCEG score recompute
  20. 2026-08-09 16:30 UTCGHSA enrichment
  21. 2026-08-09 13:47 UTCEPSS rescore
  22. 2026-08-09 03:35 UTCEG score recompute
  23. 2026-08-09 03:35 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-08 14:40 UTCGHSA enrichment
  26. 2026-08-08 01:45 UTCEG score recompute
  27. 2026-08-08 01:45 UTCGHSA enrichment
  28. 2026-08-07 12:49 UTCGHSA enrichment
  29. 2026-08-06 23:54 UTCEG score recompute
  30. 2026-08-06 23:54 UTCGHSA enrichment
  31. 2026-08-06 13:47 UTCEPSS rescore
  32. 2026-08-06 10:58 UTCGHSA enrichment
  33. 2026-08-05 22:03 UTCEG score recompute
  34. 2026-08-05 22:03 UTCGHSA enrichment
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 09:08 UTCGHSA enrichment
  38. 2026-08-04 20:13 UTCEG score recompute
  39. 2026-08-04 20:13 UTCGHSA enrichment
  40. 2026-08-04 15:10 UTCEPSS rescore
  41. 2026-08-04 10:39 UTCEPSS rescore
  42. 2026-08-04 07:18 UTCEG score recompute
  43. 2026-08-04 07:17 UTCGHSA enrichment
  44. 2026-08-03 18:18 UTCEG score recompute
  45. 2026-08-03 18:18 UTCGHSA enrichment
  46. 2026-08-03 18:00 UTCEG score recompute
  47. 2026-08-03 18:00 UTCGHSA enrichment
  48. 2026-08-03 17:04 UTCEG score recompute
  49. 2026-08-03 17:04 UTCGHSA enrichment
  50. 2026-08-03 10:36 UTCEPSS rescore
  51. 2026-08-03 04:07 UTCGHSA enrichment
  52. 2026-08-02 15:10 UTCGHSA enrichment
  53. 2026-08-02 02:15 UTCEG score recompute
  54. 2026-08-02 02:15 UTCGHSA enrichment
  55. 2026-08-01 13:19 UTCEG score recompute
  56. 2026-08-01 12:44 UTCEG score recompute
  57. 2026-08-01 12:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67331?
CVE-2026-67331 is a high vulnerability published on August 1, 2026. better-auth SCIM versions from 1.5.0 before 1.7.0-beta.4 fail to bind non-organization SCIM providers to their creator by default, allowing authenticated users to manage other users' providers. Attackers can regenerate SCIM bearer tokens, invalidate legitimate tokens, and authenticate to SCIM API…
When was CVE-2026-67331 disclosed?
CVE-2026-67331 was first published in the National Vulnerability Database on August 1, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67331 actively exploited?
CVE-2026-67331 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 84.7% of all scored CVEs.
What is the CVSS score of CVE-2026-67331?
CVE-2026-67331 has a CVSS v4.0 base score of 8.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-67331?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67331, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67331

Explore →

Is Your Infrastructure Affected by CVE-2026-67331?

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

Start Free Scan →Browse All CVEs