Skip to main content
Menu
CVEs

CVE

The Document Foundation LibreOffice code execution in ODF form control import

CVE-2026-101892EUVD-2026-126505GHSA-2GX6-PMG5-JR96

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

8.5HighCNA
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. The document is in ODF format and contains form controls, such as buttons and text fields. LibreOffice versions before 26.2.7 or 26.8.2.

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

Summary

LibreOffice can be made to run code when it opens a crafted ODF document that contains form controls, because it creates whatever component a control names and applies the stored settings to it. Exploiting this requires local access and a user action, such as opening the malicious file.

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

Original description

LibreOffice documents in ODF format can contain form controls, such as buttons and text fields, and each control names the component that implements it. The component a control named was created even when it was not a form control, and the settings stored with the control were applied to it, so a crafted document could change the configuration of LibreOffice in a way that led to code being run. In fixed versions a control whose component is not a form control is ignored.

Who should check

Teams running LibreOffice that open ODF documents containing form controls, such as buttons and text fields, including document-handling or file-sharing services.

“LibreOffice documents in ODF format can contain form controls”

libreoffice.org

cve.now Index

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

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    The document is in ODF format and contains form controls, such as buttons and text fields. LibreOffice versions before 26.2.7 or 26.8.2.
  • 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-101892 (Code execution through form control import in ODF documents), 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-101892 (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):
- The document is in ODF format and contains form controls, such as buttons and text fields. (source: https://www.libreoffice.org/security/#cve-2026-101892)
- LibreOffice versions before 26.2.7 or 26.8.2. (source: https://www.libreoffice.org/security/#cve-2026-101892)
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-101892 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101892 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-101892
- https://www.libreoffice.org/security/#cve-2026-101892
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-101892
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-101892"}.

Timeline

  1. CISA SSVC assessment

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

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

Is CVE-2026-101892 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 crafted ODF document can contain form controls that change LibreOffice's configuration, which can lead to code being run on the computer opening it.Source: libreoffice.org

Which versions are affected by CVE-2026-101892?

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

How do I fix CVE-2026-101892?

Upgrade to a fixed version: < 26.2.7, < 26.8.2. The vendor's advisory also recommends 26.2.7 or 26.8.2 or later.Source: cve.now feed data, libreoffice.org