How severe is GHSA-84vh-m24q-wjjx?

No CVSS score has been assigned to GHSA-84vh-m24q-wjjx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-84vh-m24q-wjjx?

GHSA-84vh-m24q-wjjx affects the following packages: github.com/pocketbase/pocketbase (Go), github.com/pocketbase/pocketbase (Go). Ecosystems affected: Go.

How do I fix GHSA-84vh-m24q-wjjx?

Update github.com/pocketbase/pocketbase to 0.22.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84vh-m24q-wjjx is resolved across your whole dependency graph.

How do I detect GHSA-84vh-m24q-wjjx 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-84vh-m24q-wjjx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-84vh-m24q-wjjx actively exploited in the wild?

No public exploit code has been indexed for GHSA-84vh-m24q-wjjx 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-84vh-m24q-wjjx?

GHSA-84vh-m24q-wjjx has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th 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-84vh-m24q-wjjx?

GHSA-84vh-m24q-wjjx is classified as CWE-248 (CWE-248). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-84vh-m24q-wjjx published, and has it been updated?

GHSA-84vh-m24q-wjjx was published on September 17, 2026 and was last updated on October 7, 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: Unhandled panic in worker goroutinesGHSA-84vh-m24q-wjjx

Fix: pocketbase/pocketbase@30b4184

GHSA-84vh-m24q-wjjx is a CWE-248 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-82410GO-2026-6489

Published

Sep 17, 2026

Updated

Oct 7, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-84vh-m24q-wjjx.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% 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

To prevent this from hapenning all existing internal worker functions were wrapped with the new helper routine.SafeWrap(f) (auto recovers and returns any eventual panic as regular error).

The vulnerability was reported by @gigioneggiando and it is strongly recommended to upgrade to PocketBase v0.39.7 (the fix was also backported in v0.22.48 in case you are using older PocketBase < v0.23.0).

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/pocketbase/pocketbase`	all versions	0.22.48`go get github.com/pocketbase/pocketbase@v0.22.48`
🐹Go	`github.com/pocketbase/pocketbase`	≥ 0.23.0&&< 0.39.7	0.39.7`go get github.com/pocketbase/pocketbase@v0.39.7`

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.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84vh-m24q-wjjx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

PocketBase already has builtin panic-recover middleware for the regular requests handling but it doesn't cover panics in internal child/worker goroutines which in some situations could cause termination of the server process. To prevent this from hapenning all existing internal worker functions were wrapped with the new helper `routine.SafeWrap(f)` _(auto recovers and returns any eventual panic as regular error)_. The vulnerability was reported by @gigioneggiando and it is strongly recommended to upgrade to PocketBase **[v0.39.7](https://github.com/pocketbase/pocketbase/releases/tag/v0.39.7)

O3 Security · Impact-Aware SCA

Is GHSA-84vh-m24q-wjjx in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works