Skip to main content
Menu
CVEs

CVE

The Document Foundation LibreOffice key recovery in PDF password export encryption

CVE-2026-18564

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

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in < 26.2.6
Who is exposed
Not reported

Do first: Upgrade to a fixed version: < 26.2.6.

Published
Last modified
Reference
Last checked
24/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

LibreOffice's PDF 2.0 password export uses a random number generator that is not suitable for cryptography to create the file encryption key and salts. An attacker can recover the key of an exported PDF without knowing the password, and can do this remotely without logging in.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: < 26.2.6.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-18564 (Weak random numbers used for PDF 2.0 encryption keys), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-18564 (entry last updated 2026-11-16):
Affected:
- The Document Foundation LibreOffice: from 26.2, fixed in < 26.2.6
Fixed versions: < 26.2.6.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-18564 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-18564 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.libreoffice.org/about-us/security/advisories/cve-2026-18564
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-18564
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-18564"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • The Document Foundation LibreOffice

    From 26.2 · fixed in < 26.2.6

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-18564

Is CVE-2026-18564 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-18564?

LibreOffice: from 26.2 before < 26.2.6.Source: cve.now feed data

How do I fix CVE-2026-18564?

Upgrade to a fixed version: < 26.2.6.Source: cve.now feed data