CVE-2026-67331
Auth SCIM bug lets authenticated users manage others' SCIM providers and mint bearer tokens.
Is CVE-2026-67331 being exploited?
Not confirmed. CVE-2026-67331 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-67331?
CVE-2026-67331 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67331?
Yes. A fix has been recorded for CVE-2026-67331. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67331 affect?
CVE-2026-67331 affects better-auth SCIM versions >=1.5.0 and <1.7.0-beta.4, Applications using affected better-auth SCIM builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67331?
Upgrade to >=1.7.0-beta.4, rotate SCIM bearer tokens, audit provider bindings
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can bind/manage other users' SCIM providers, regenerate/invalidate SCIM bearer tokens, and access SCIM API as victims.
Patch when possible
- affected>= 1.5.0 and < 1.7.0-beta.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.