Loading vulnerability…
CVE-2026-67330 is a critical authorization bypass in the @better-auth/scim plugin affecting versions 1.4.0-beta.27 through 1.6.21 and 1.7.0-beta.0 through 1.7.0-beta.9. The flaw arises because SCIM token issuance failed to reject provider IDs that were already in use by existing SSO, SAML, OIDC, generic OAuth, or social account providers, while the same logical provider ID was also used to resolve account ownership. As a result, an authenticated user could mint a SCIM token with a provider ID that collided with an existing provider namespace. When that token was used against SCIM user routes, the application could resolve and operate on account rows that were never provisioned by that token. This broke authorization boundaries across provider namespaces and exposed global user and session records to unauthorized SCIM operations.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.