Stack Watch
Self-hosted update briefs — is it safe to update, or wait?
Disclaimer: Automated heuristics over public release notes and vulnerability databases (OSV / NVD). Can be wrong or incomplete. Always back up first and validate upgrades yourself. Stack Watch does not invent CVE IDs or issue counts. This is an MVP research project, not a live paid service.
Home / Paperless-ngx / v3.3.1

Paperless-ngx v3.3.1

SAFE

No breaking/security/wait signals detected in release notes heuristics.

Published: 2026-10-12T20:22:04Z · GitHub release

Summary of changes

## paperless-ngx 3.3.1 ## Bug Fixes - Fix: use a root document's effective content for the LLM index and pr… @stumpylog (#14423) - Fix: index document versions as their root document @stumpylog (#14422) - Fix: authorize document versions by their root in the single-object permission check @stumpylog (#14421) - Fix: Provide better error messages to users for invalid JSON @stumpylog (#14419) - Fix: authorize document versions by their root and speed up permission id sets @stumpylog (#14396) - Chore: update the db options warning @shamoon (#14398) - Fix: bulk reprocess latest version for root documents @shamoon (#14385) - Fix: consistently use root doc for version action permissions @shamoon (#14384) - Fix: Don't attempt to index created dates which are not representable in the FTS index @stumpylog (#14390) - Fix: retry a search index rebuild that was interrupted @stumpylog (#14379) …

Breaking changes

None detected by heuristics.

CVEs linked to this release

None linked from release notes or OSV fixed-in match.

Linked issues / PRs mentioned

16

Back up first

Always back up first. Stack Watch briefs are automated heuristics over public release notes and vulnerability databases. They can be wrong or incomplete. You are responsible for validating upgrades in your own environment. We never invent CVE IDs or issue counts — if a number is missing, it was not found.