Impact Score: 5/10
PocketBase: v0.22.57 Release
Source available โ automated, not human-reviewed
Component: pocketbase ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.
Analysis updated: 2026-10-31.
โก Executive Summary (TL;DR)
PocketBase v0.22.57. Source highlight: (_Backported from v0.40.6_) Added a global restriction for the max `WxH` pixels size when generating a thumb to reduce the risk of excessive memory usage.
Who Does This Impact? (Role-Based Analysis)
๐ป Software Engineers & Devs
Check the source notes against the package and APIs you use before upgrading.
๐ Product & Engineering Leads
Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.
โ๏ธ DevOps & Security
Verify the target version, runtime requirements and rollback procedure in the official documentation.
โจ New Features & Capabilities (1)
- (_Backported from v0.40.6_) Added a global restriction for the max `WxH` pixels size when generating a thumb to reduce the risk of excessive memory usage.
๐ง Bug Fixes & Patches (1)
- (_Backported from v0.40.6_) Bumped the min Go GitHub action version to 1.27.3 as it includes a security fix related to the recent eMudhra CA compromise.
๐ View Raw Release Notes (Original Developer Log)
- (_Backported from v0.40.6_) Added a global restriction for the max `WxH` pixels size when generating a thumb to reduce the risk of excessive memory usage.
The default limit is pretty generous and currently set to max `250<<20 (262144000)` pixels and can be changed with the env `PB_THUMBS_MAX_SOURCE_PIXELS`.
- (_Backported from v0.40.6_) Bumped `golang.org/x/` dependencies ([#7865](https://github.com/pocketbase/pocketbase/discussions/7865)).
- (_Backported from v0.40.6_) Bumped the min Go GitHub action version to 1.27.3 as it includes a [security fix](https://groups.google.com/g/golang-announce/c/66pojueaQek) related to the recent eMudhra CA compromise.
_I didn't rush a fix 2 days ago as the impact for most PocketBase servers is not that serious and requires to already have a MiTM, but nonetheless it is recommended to update. Please make sure to also check for OS/Docker image updates to make sure that you have the latest `ca-certificates` bundle._