As of 17 November 2026. The Document Foundation says LibreOffice 26.8.3, released on 12 November, restores signing with X.509 certificates. The statement appears in the announcement’s macOS paragraph; it is not evidence that every platform had the same defect or that every signing failure is fixed. Offices exchanging signed documents need a repeatable sender-and-recipient check, not just a newer version number. [1]
What the fix does – and does not do
A digital signature is not a pasted signature image or encryption. It can reveal changes to signed content; certificate trust and the signer’s identity still need checking. The help distinguishes an invalid signature from a certificate chain that cannot be fully validated. OOXML signing does not cover every component: metadata is excluded according to the help. A warning is not permission to disable verification. [3]
Prerequisites and recovery
Use an approved device, an already authorised personal certificate with its securely managed private key, a harmless ODF test document and a second approved checking environment. Never upload private keys or export passwords to support sites. Back up originals separately and record the starting version, certificate reference and installation source. IT needs a practical route back to the previous installation/system state; a document copy is not a system backup.
Five verification steps
- Record the baseline: full version from the About dialog, operating system, architecture and exact previous error. Use managed software deployment on company devices. Reproduce only with a non-confidential copy; leave production signatures and originals untouched.
- Update through the approved channel: use the appropriate 26.8.3 package or a vendor package explicitly documented as containing the corresponding correction. Do not mix Linux distribution packages with unrelated repositories; distinguish Intel and Apple Silicon on macOS. Check the actual package requirements. Restart LibreOffice and read the version again. [2][5]
- Inspect the certificate: check that the signing dialog offers the expected certificate, its issuer and validity period. The help describes the Windows system certificate store and Firefox/Thunderbird profiles plus certificate-path selection for Linux/macOS. Do not blindly change profiles, import unfamiliar roots or expand trust. Escalate a missing certificate to IT. [4]
- Sign a test copy: save a new ODF document, then use File → Digital Signatures → Digital Signatures to select the existing certificate. Labels may vary by interface. Close and reopen the file, then inspect status and certificate details. Use test data only and do not enable unknown macros. [4]
- Check receipt and modification separately: open the unchanged test file in the approved second environment and confirm the expected signer. Save a further copy with changed content and check again: it must not pass as unchanged and validly signed. Re-signing would test a new signature rather than the original. Accept ODF, OOXML and PDF as separate workflows. [3]
Acceptance and safe diagnosis
Accept the pilot only after recording the package version, correct certificate, recipient verification and detection of changed test content. If it fails, record format, version, time and exact status without sharing confidential files or keys. Separate certificate expiry, trust-chain and document-change problems. Pause deployment and use only the prepared recovery route; preserve originals and do not bypass warnings.
Limits and sources
Editorial verification guide, not an installation/signature test performed by us or a legal assessment. The RC1 details could not be read; no individual bug ID or universal platform impact is asserted. The release overview still labels 26.2.7 an enterprise branch, while the newer announcement recommends migration before 30 November; that older description does not extend maintenance. [1][2] Manufacturer links only; no affiliate links.
