Authentication Bypass in github.com/pocketbase/pocketbase (CVE-2026-44166)
Summary
Authentication bypass in github.com/pocketbase/pocketbase (CVE-2026-44166). Data can be tampered with by attackers. Mitigation: upgrade to 0.37.4 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44166 has been found in github.com/pocketbase/pocketbase.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: upgrade github.com/pocketbase/pocketbase to 0.37.4 or later.
If unsure, ask your IT team or search "github.com/pocketbase/pocketbase CVE-2026-44166" on the vendor's site.
CVE-2026-44166 (github.com/pocketbase/pocketbase) — CWE-287 / CVSS v3 7.6
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.37.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in github.com/pocketbase/pocketbase.
Check the vendor advisory for the affected versions of github.com/pocketbase/pocketbase.
Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.
Update to 0.37.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/pocketbase/pocketbase' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/pocketbase/pocketbase' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/pocketbase/pocketbaseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/pocketbase/pocketbase to 0.37.4ステージング環境で 0.37.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com