Summary
Pocketbase: Unhandled panic in worker goroutines
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 (the fix was also backported in v0.22.48 in case you are using older PocketBase < v0.23.0).
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
github.com/pocketbase/pocketbase to 0.22.48 or later; github.com/pocketbase/pocketbase to 0.39.7 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-82410? CVE-2026-82410 is a high-severity security vulnerability in github.com/pocketbase/pocketbase (go), affecting versions < 0.22.48. It is fixed in 0.22.48, 0.39.7.
- Which versions of github.com/pocketbase/pocketbase are affected by CVE-2026-82410? github.com/pocketbase/pocketbase (go) versions < 0.22.48 is affected.
- Is there a fix for CVE-2026-82410? Yes. CVE-2026-82410 is fixed in 0.22.48, 0.39.7. Upgrade to this version or later.
- Is CVE-2026-82410 exploitable, and should I be worried? Whether CVE-2026-82410 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-82410 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-82410?
- Upgrade
github.com/pocketbase/pocketbaseto 0.22.48 or later - Upgrade
github.com/pocketbase/pocketbaseto 0.39.7 or later
- Upgrade