Is Paperless-ngx v3.4.1 safe to update?

Probably yes. Bug fixes and minor features only, per the release notes. No breaking changes mentioned.

What users are reporting

6 public report(s) mention this version, none clearly describing breakage. Most-discussed: “[BUG] Current container image (v3.4.1) ships vulnerable version of libnss3”. Sources: GitHub · checked 2026-11-02

• [BUG] Current container image (v3.4.1) ships vulnerable version of libnss3 (GitHub, closed)
• [BUG] Dates written with spaces after the dots (15. 10. 2026) are not detected as the document date (GitHub, closed)
• [BUG] Tags are displayed as IDs in the document history when changed via the document list (GitHub, closed)
• [BUG] Object name search is case-sensitive for non-ASCII characters (umlauts) (GitHub, closed)
• [BUG] Merge with "Delete original documents" never deletes originals, task stays pending (GitHub)

Reports are from public issue trackers and forums. Their count isn't a failure rate, and an empty list doesn't prove an update is safe.

⚠️ What breaks

Nothing in the release notes suggests breaking changes. This looks like a bug-fix or minor release. The usual precautions (backup, read notes) still apply.

Read the full official release notes →

✅ What to do first

1. Read the official release notes (linked in “What breaks”).
2. Back up config and data (snapshot the VM/volume if you can).
3. Note the version you are on now, so you can roll back.
4. Update, then check logs and core functions before walking away.

↩️ How to roll back to v3.4.0

Docker: snapshot/back up the data volumes first, then if needed change the tag back, e.g. image: ghcr.io/paperless-ngx/paperless-ngx:v3.4.0, and run docker compose up -d. Tag format varies by image (some drop the “v”), so check the registry’s tag list.