Is CVE-2026-67331 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67331 being exploited in the wild.

How severe is CVE-2026-67331?

High severity, with a CVSS score of 8.3, published 1 August 2026.

Which products and versions are affected?

@better-auth/scim (npm) SEMVER:introduced=1.5.0,fixed=1.7.0-beta.4.

Is there a fix for CVE-2026-67331?

Yes. @better-auth/scim (npm): upgrade to 1.7.0-beta.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67331 attacked?

It is attacked over the network.

Am I affected by CVE-2026-67331?

Check whether you run @better-auth/scim (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67331: Better Auth SCIM provider takeover via missing owner binding

CVE-2026-67331 · Severity: high · CVSS 8.3 · Published 2026-08-01

Better Auth's SCIM plugin manages identity provider integrations for organizations. By default, non-organizational SCIM providers lack owner validation, allowing any authenticated user in a multi-user deployment to read, regenerate tokens for, and effectively take control of another user's provider. This enables account takeover and provider impersonation without elevated privileges.

Vendors: npm.

Quick answers

Is CVE-2026-67331 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67331 being exploited in the wild.
How severe is CVE-2026-67331?: High severity, with a CVSS score of 8.3, published 1 August 2026.
Which products and versions are affected?: @better-auth/scim (npm) SEMVER:introduced=1.5.0,fixed=1.7.0-beta.4.
Is there a fix for CVE-2026-67331?: Yes. @better-auth/scim (npm): upgrade to 1.7.0-beta.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67331 attacked?: It is attacked over the network.
Am I affected by CVE-2026-67331?: Check whether you run @better-auth/scim (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@better-auth/scim (npm): upgrade to 1.7.0-beta.4 or later
```
npm install @better-auth/scim@1.7.0-beta.4
```

Technical details

The vulnerability is an authorization bypass in the @better-auth/scim plugin affecting non-organization SCIM providers. The access control check for SCIM management operations (token generation/regeneration, provider reads, deletions) is flawed: it only denies access when a stored userId exists AND differs from the caller. By default, the scimProvider.userId column is unset and the providerOwnership option is disabled, so the check passes for all authenticated users. This affects all management endpoints reachable through the public API. The most critical impact is token regeneration: an attacker can regenerate a provider's SCIM bearer token, invalidating the legitimate owner's token and gaining authentication to that provider's SCIM API routes. The attack requires multiple authenticated users in the deployment and is not exploitable in single-tenant scenarios. Patches are available in @better-auth/scim@1.7.0-beta.4 and later, which make owner binding mandatory.

Affected products

Better Auth @better-auth/scim 1.5.0 through 1.7.0-beta.3

Identifiers

CVE-2026-67331
GHSA-j8v8-g9cx-5qf4

Timeline

2026-07-07: disclosed
2026-07-07: patched: 1.7.0-beta.4 released with fix; 1.7.0 stable to follow

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.