Pocketbase up to 0.22.41/0.37.3 Password Reset improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Pocketbase up to 0.22.41/0.37.3. It has been classified as critical. This affects an unknown function of the component Password Reset Handler. The manipulation leads to improper authentication. This vulnerability is referenced as CVE-2026-44166. Remote exploitation of the attack is possible. Furthermore, an exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, has been found in Pocketbase up to 0.22.41/0.37.3. This issue affects an unknown code block of the component Password Reset Handler. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-44166 since 05/05/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.
The exploit is available at github.com. It is declared as proof-of-concept.
Upgrading to version 0.22.42 or 0.37.4 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 0.22.0
- 0.22.1
- 0.22.2
- 0.22.3
- 0.22.4
- 0.22.5
- 0.22.6
- 0.22.7
- 0.22.8
- 0.22.9
- 0.22.10
- 0.22.11
- 0.22.12
- 0.22.13
- 0.22.14
- 0.22.15
- 0.22.16
- 0.22.17
- 0.22.18
- 0.22.19
- 0.22.20
- 0.22.21
- 0.22.22
- 0.22.23
- 0.22.24
- 0.22.25
- 0.22.26
- 0.22.27
- 0.22.28
- 0.22.29
- 0.22.30
- 0.22.31
- 0.22.32
- 0.22.33
- 0.22.34
- 0.22.35
- 0.22.36
- 0.22.37
- 0.22.38
- 0.22.39
- 0.22.40
- 0.22.41
- 0.37.0
- 0.37.1
- 0.37.2
- 0.37.3
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.1
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.6
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Pocketbase 0.22.42/0.37.4
Timeline
05/05/2026 CVE reserved05/12/2026 Advisory disclosed
05/12/2026 VulDB entry created
05/20/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-pq7p-mc74-g65w
Status: Confirmed
CVE: CVE-2026-44166 (🔒)
GCVE (CVE): GCVE-0-2026-44166
GCVE (VulDB): GCVE-100-363305
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/12/2026 20:47Updated: 05/20/2026 09:57
Changes: 05/12/2026 20:47 (38), 05/12/2026 20:48 (32), 05/20/2026 09:57 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.