Pocketbase
Pocketbase: Account pre-hijacking via OAuth2 unverfied->verified autolinking upgrade
Pocketbase is an open source web backend written in go. Prior to 0.22.42 and 0.37.4, in some situations, if an attacker knows the email address of the victim they can create and link an unverified PocketBase user in advance by authenticating with one of the OAuth2 app providers, e.g. "A". When the victim gets invited or decides to sign up to your app on their own with provider "B" (PocketBase OAuth2 auth requires to be with a different provider because we don't allow multiple OAuth2 accounts from the same provider to be associated to a single PocketBase user), the user created previously by the attacker will be autolinked, upgraded to "verified" and its old password reset. This vulnerability is fixed in 0.22.42 and 0.37.4.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.22.42
- >= 0.30.0, < 0.37.4
Fixed in 0.22.42, 0.37.4
Mitigation
Upgrade pocketbase to 0.22.42 or 0.37.4 or later.
References
- Vendor advisory github.com/pocketbase/pocketbase/security/advi…
Timeline
Days relative to CVE publicationFirst public PoC 29 days after publication; not in CISA KEV. First PoC: Alardiians/pocketbase-CVE-2026-44166 (created 11 Jun 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Alardiians/pocketbase-CVE-2026-44166 | 11 Jun 2026 +29 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.