FileRise

v3.22.0 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 14d File Storage & Sync

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

acl docker file-editor file-manager file-upload folder-management

+11 more

javascript multi-file-upload php self-hosted sso twofactor-auth unraid uploader web web-based webdav

Affected surfaces

auth

Summary

AI summary

Updates v3.22.0, https://github.com/error311/FileRise/compare/v3.21.0...v3.22.0, and zip across a mixed release.

Changes in this release

Type	Severity	Summary	CVE
Bugfix
Bugfix	Medium	Pristine manual installs now generate and persist a unique persistent-tokens key. Pristine manual installs now generate and persist a unique persistent-tokens key. Source: llm_adapter@2026-07-13 Confidence: high	—
Bugfix	Medium	Concurrent first requests coordinate key creation to ensure all workers use the same persisted key. Concurrent first requests coordinate key creation to ensure all workers use the same persisted key. Source: llm_adapter@2026-07-13 Confidence: high	—
Bugfix	Medium	Docker aborts with an actionable error when a pristine key cannot be persisted. Docker aborts with an actionable error when a pristine key cannot be persisted. Source: llm_adapter@2026-07-13 Confidence: high	—
Bugfix	Low	Existing environment keys and installations retain current behavior during upgrade for compatibility. Existing environment keys and installations retain current behavior during upgrade for compatibility. Source: llm_adapter@2026-07-13 Confidence: high	—
Bugfix	Low	Admin Panel continues to show warning and controlled rotation workflow for legacy installs. Admin Panel continues to show warning and controlled rotation workflow for legacy installs. Source: llm_adapter@2026-07-13 Confidence: high	—
Bugfix	Low	Upgrade notes recommend backing up `metadata/persistent_tokens.key` with other metadata files. Upgrade notes recommend backing up `metadata/persistent_tokens.key` with other metadata files. Source: llm_adapter@2026-07-13 Confidence: high	—

Full changelog

Changes 07/13/2026 (v3.22.0)

release(v3.22.0): generate unique keys for pristine manual installs

Fixed

Pristine manual installs now generate and persist a unique persistent-tokens key instead of beginning with the published legacy fallback.
Existing environment keys, persisted key files, Docker source hints, and installations with existing state retain their current key behavior for upgrade compatibility.
Concurrent first requests coordinate key creation so every worker uses the same persisted key, and Docker now stops with an actionable error if a pristine key cannot be persisted.

Upgrade notes

Existing legacy installs are not rotated automatically; the Admin Panel warning and controlled rotation workflow remain available.
Back up metadata/persistent_tokens.key with the rest of the metadata directory.

v3.22.0

Full Changelog

v3.21.0 → v3.22.0

SHA-256 (zip)

c28c6b6bd4175538c203a43981e72987dc8b7270ddacfc4ffa226344ce50633e  FileRise-v3.22.0.zip

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track FileRise

Get notified when new releases ship.

About FileRise

FileRise – lightweight, self-hosted file manager & storage hub with granular ACLs, resumable uploads, encrypted folders, WebDAV & SSO. Fully Docker / Unraid compatible.

All releases →