CVE-2026-18564 · Runtime
NO FIX YET
When LibreOffice exports a password-protected PDF with the PDF 2.0 option, the 256-bit AES encryption key and salts come from a pseudo-random generator that is not suitable for cryptography. An attacker could recover the encryption key of an exported PDF without knowing the password.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only documents exported to PDF with a password and the PDF 2.0 option are affected, since that option uses the weak key and salt generation. Teams that do not export password-protected PDF 2.0 files from LibreOffice can skip it. The sources do not name the fixed versions, so unknown.
Not affected if no-password-pdf-export, pdf-1.x-export
Who cares libreoffice, office-documents
Unknown from the sources.
LibreOffice can export documents to PDF protected by a password. With the PDF 2.0 option the file is encrypted with 256-bit AES, using a file encryption key and salts that are meant to be random. The key and the salts were drawn from a pseudo-random number generator that is not suitable for cryptography, so the encryption key of an exported PDF could be recovered without knowing the password. In fixed versions the key and the salts are drawn from the random source of the operating system.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.