How severe is GHSA-pq7p-mc74-g65w?

No CVSS score has been assigned to GHSA-pq7p-mc74-g65w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-pq7p-mc74-g65w?

GHSA-pq7p-mc74-g65w affects the following packages: github.com/pocketbase/pocketbase (Go), github.com/pocketbase/pocketbase (Go). Ecosystems affected: Go.

How do I fix GHSA-pq7p-mc74-g65w?

Update github.com/pocketbase/pocketbase to 0.22.42 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pq7p-mc74-g65w is resolved across your whole dependency graph.

How do I detect GHSA-pq7p-mc74-g65w in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pocketbase/pocketbase, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-pq7p-mc74-g65w if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-pq7p-mc74-g65w actively exploited in the wild?

No public exploit code has been indexed for GHSA-pq7p-mc74-g65w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-pq7p-mc74-g65w?

GHSA-pq7p-mc74-g65w has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-pq7p-mc74-g65w?

GHSA-pq7p-mc74-g65w is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pq7p-mc74-g65w published, and has it been updated?

GHSA-pq7p-mc74-g65w was published on May 5, 2026 and was last updated on July 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

PocketBase vulnerable to account pre-hijacking via OAuth2 unverfied->verified autolinking upgradeGHSA-pq7p-mc74-g65w

GHSA-pq7p-mc74-g65w is a Improper Authentication vulnerability in github.com/pocketbase/pocketbase. A fix is available for github.com/pocketbase/pocketbase — see the affected versions and patch details below.

Also known asCVE-2026-44166GO-2026-5548

Published

May 5, 2026

Updated

Jul 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pq7p-mc74-g65w.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐹github.com/pocketbase/pocketbase🐹github.com/pocketbase/pocketbase

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A pre-hijacking issue was discovered with the OAuth2 autolinking by Alardiians.

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.

The upgrade flow operates within the expectations but the problem is that I forgot to clear the previous OAuth2 link(s) leaving the attacker to still have access to the initially created user.

Or in other words, the vulnerability is similar to the mixed password + OAuth2 auth pre-hijacking issue that we had in the past but with a slightly different angle.

So with that in mind, and to avoid introducing breaking changes to the auth flows, a new fix was applied that automatically deletes all such pre-existing OAuth2 links on "unverified" to "verified" upgrades.

While the vulnerability requires some prerequisites, it is considered severe and it is strongly recommended to upgrade to v0.37.4 (or to v0.22.42 if you are using an older <v0.23.0 release).

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/pocketbase/pocketbase`	all versions	0.22.42`go get github.com/pocketbase/pocketbase@v0.22.42`
🐹Go	`github.com/pocketbase/pocketbase`	≥ 0.30.0&&< 0.37.4	0.37.4`go get github.com/pocketbase/pocketbase@v0.37.4`

Affected Products

1 product · 2 configurations

Application

pocketbasepocketbase

≥ 0.23.0 && < 0.37.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pocketbase/pocketbase, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/pocketbase/pocketbase to 0.22.42 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pq7p-mc74-g65w is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

A pre-hijacking issue was discovered with the OAuth2 autolinking by [Alardiians](https://github.com/Alardiians). 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)_

O3 Security · Impact-Aware SCA

Is GHSA-pq7p-mc74-g65w in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works