PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-82410 – Denial of Service (Unhandled Panic) – PocketBase before 0.22.48 / 0.23.0–0.39.6

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82410 is a denial-of-service vulnerability in PocketBase, the open-source Go backend framework, caused by an unhandled panic in internal worker goroutines. The flaw allows a remote, unauthenticated attacker to crash the PocketBase server process. It carries a CVSS score of 8.7 (High).

Technical details

  • PocketBase’s panic-recovery middleware is applied only to regular HTTP request handling, not to internal child and worker goroutines spawned by the application.
  • A panic triggered inside one of these internal worker goroutines is not caught by the recovery middleware and propagates unhandled, crashing the entire server process.
  • The vulnerability is remotely triggerable over the network, requires no authentication, and needs no user interaction, giving it a low attack complexity.
  • Impact is limited to availability: successful exploitation terminates the running PocketBase instance, causing a full service outage until the process is restarted.
  • Classified under CWE-248 (Uncaught Exception).

Affected software

  • PocketBase versions prior to 0.22.48
  • PocketBase versions 0.23.0 through 0.39.6

Severity

  • CVSS 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to PocketBase 0.22.48 (for the 0.22.x line) or 0.39.7 (for later releases), both of which wrap internal worker functions with a routine.SafeWrap helper that recovers panics and converts them into regular errors instead of crashing the process.
  • If no patch: There is no supported workaround that fully prevents the underlying unhandled panic; organizations unable to patch immediately should place PocketBase instances behind a process supervisor/orchestrator configured for automatic restart on crash, and restrict network exposure of the service to trusted sources to reduce the window for repeated exploitation until the upgrade is applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge