Skip to main content
Menu
CVEs

CVE

The Document Foundation LibreOffice command injection in document email via file name

Affects LibreOffice 26.2 before 26.2.7 and 26.8 before 26.8.2 on Linux and other Unix-like systems when a document is sent with File > Send > Email Document. Fixed in 26.2.7 and 26.8.2.

CVE-2026-100101EUVD-2026-126502GHSA-2WR6-W3F2-HH4X

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

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

8.4HighCNA
Exploited
No known exploitation
Fix
Fixed in < 26.2.7, < 26.8.2
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. LibreOffice running on Linux or other Unix-like systems The document is sent by email using File > Send > Email Document

Published
Last modified
Reference
Last checked
14/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

A command injection flaw in The Document Foundation's LibreOffice lets a local attacker, without logging in, run commands on Linux and other Unix-like systems. It is triggered when a user emails a document with a crafted file name using File > Send > Email Document, because the bundled script let the shell interpret that name.

Original description

On Linux and other Unix-like systems, LibreOffice can send the current document as an email attachment with File > Send > Email Document, which starts the mail client through a script bundled with LibreOffice. The script let the shell interpret the name of the document's file, so a file with a crafted name could run commands when it was sent by email. In fixed versions the script passes the file name and the other details to the mail client as plain arguments.

Who should check

Teams running LibreOffice on Linux or other Unix-like systems who use File > Send > Email Document to email documents

“On Linux and other Unix-like systems, LibreOffice can send the current document as an email attachment”

libreoffice.org

cve.now Index

14Pcve.now Index 14 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.4/10CVSS 8.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 64 if added to CISA KEV
  • Would score about 59 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    LibreOffice running on Linux or other Unix-like systems The document is sent by email using File > Send > Email Document
  • Upgrade to a fixed version: < 26.2.7, < 26.8.2.

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-100101 (Command injection through the file name when emailing a document), 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-100101 (entry last updated 2026-11-17):
Affected:
- The Document Foundation LibreOffice: from 26.2, fixed in < 26.2.7; from 26.8, fixed in < 26.8.2
Fixed versions: < 26.2.7, < 26.8.2.
Conditions (all must be true for the bug to be hit):
- LibreOffice running on Linux or other Unix-like systems (source: https://www.libreoffice.org/security/#cve-2026-100101)
- The document is sent by email using File > Send > Email Document (source: https://www.libreoffice.org/security/#cve-2026-100101)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-100101 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-100101 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-100101
- https://www.libreoffice.org/security/#cve-2026-100101
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-100101
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-100101"}.

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

    6 days
  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

Affected versions

  • The Document Foundation LibreOffice

    From 26.2 · fixed in < 26.2.7; From 26.8 · fixed in < 26.8.2

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-100101

Is CVE-2026-100101 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

What does this mean?

A file with a crafted name could run commands on the system when the document is sent by email using File > Send > Email Document. The email step starts the mail client through a script bundled with LibreOffice.Source: libreoffice.org

Which versions are affected by CVE-2026-100101?

LibreOffice: from 26.2 before < 26.2.7; from 26.8 before < 26.8.2.Source: cve.now feed data

Am I affected, and how do I check?

The affected ranges are LibreOffice 26.2 before 26.2.7 and 26.8 before 26.8.2, on Linux and other Unix-like systems. To check a version, open Help > About LibreOffice and compare the number with these ranges.Source: libreoffice.org

How do I fix CVE-2026-100101?

Upgrade to LibreOffice 26.2.7 or later if you are on the 26.2 branch, or to 26.8.2 or later on the 26.8 branch.Source: libreoffice.org