CVE-2026-44166 MEDIUM

CVE-2026-44166: Pocketbase: Account pre-hijacking via OAuth2 unverfied->verified autolinking upgrade

Vendor Pocketbase
Product pocketbase
Weakness CWE-287 · Improper authentication
Published May 12, 2026
Last update May 12, 2026

CVSS base score

6.1/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction
Confidentiality
Integrity

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N

What the vulnerability does

01Description

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.

Key dates

02Disclosure timeline

May 12, 2026 CVE published
May 12, 2026 Record updated