← back
CVE-2026-44166mediumCWE-287

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

33Vexday Risk Score

No sign of exploitation. It has a public proof of concept.

ssvc Attendcvss 6.1epss 0.2%
from disclosure to weapon30 days
Published on NVDMay 12
1st PoC+30d
exploitation probability
0.2%top 84% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
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.
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
Affected products
pocketbase · pocketbase
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.