This release closes out a major security hardening effort spanning authentication, data storage, and API protections, alongside two container image CV
 Dispatchr 0.4.6dispatchr.social 0.4.6 |
This release closes out a major security hardening effort spanning authentication, data storage, and API protections, alongside two container image CVE fixes. It also fixes a Mailgun webhook error-reporting bug, adds automatic recovery from Redis outages, and standardizes pagination in the public API (a breaking change for integrators). • Major security hardening: mandatory 2FA on all admin/API routes, encryption at rest, session revocation on removal, and stricter rate limiting • Fixed a Docker image mismatch that kept a patched Next.js version from actually reaching production • Patched a denial-of-service vulnerability in the worker image's file-extraction library • Redis outages no longer cause lasting failures - the app now recovers automatically once Redis is back • Breaking: public API list endpoints now use a standardized pagination format |
New Mandatory two-factor authentication on all admin and API access Every /api/* endpoint, including platform admin routes, now enforces 2FA, closing a gap where those routes could previously be reached without a second factor. |
|
Improved Runtime images now match tested, patched dependency versions The production Docker image was pinned to an older Next.js build that never received a CVE fix already present in our lockfile. Both are now aligned (Next.js 15.5.25, Prisma 6.19.3), and a safeguard was added to catch future drift between the two. |
Worker image hardened against a tar-based denial-of-service bug Updated bundled tooling in the worker image to remove a gzip-bomb vulnerability in the file-extraction library used at build time. |
Broad security hardening across authentication, data, and API layers A member's active sessions are now revoked the moment they're removed or demoted; sensitive data is encrypted at rest with rotating keys; invitation tokens are hashed in the database; passkey login attempts are capped; and tighter request-size limits, rate limiting, CORS rules, and redirect/health-endpoint protections close a set of previously tracked security gaps (see internal security remediation tracker for full detail). |
Standardized pagination and list responses in the public API (breaking change) v1 API list endpoints now return a consistent pagination shape. Integrations using these endpoints will need to update to the new response format. |
|
Fixed Mailgun webhook errors now show the actual cause Webhook checks correctly respect read-only mode and now surface the real failure reason instead of masking it. |
Redis reconnects automatically after an outage Previously, a Redis outage could leave the app stuck in a failing state even after Redis recovered. It now resumes normal operation on its own. |
|
Where it's live Web — live
You're receiving this because you subscribed to dispatchr.social product updates. Unsubscribe |
|
|