Skip to main content
Menu
CVEs

CVE

The Document Foundation LibreOffice macro security check bypass for HTML document events

CVE-2026-101930

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. LibreOffice Writer opens the HTML document. The HTML document binds macros to document-wide events such as being opened or closed.

Published
Last modified
Reference
Last checked
14/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

LibreOffice from The Document Foundation runs macros bound to events of an HTML document, such as opening or closing it, without the macro security check, so they can run on opening whatever the macro security level. A local attacker can trigger this without logging in, but only if a user opens the malicious HTML document.

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

Original description

LibreOffice Writer can open HTML documents, and an HTML document can bind macros to events of the document as a whole, such as the document being opened or closed. Macros bound to these events were not taken into account by the macro security check, so they could run when the document was opened, whatever the macro security level. In fixed versions these macros follow the macro security settings like any other macro in the document.

Who should check

Teams running LibreOffice Writer that open HTML documents, such as users handling HTML files from outside sources, before LibreOffice 26.2.7 or 26.8.2.

“LibreOffice Writer can open HTML documents”

libreoffice.org

cve.now Index

14Pcve.now Index 14 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 8.5
  • 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 Writer opens the HTML document. The HTML document binds macros to document-wide events such as being opened or closed.
  • 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-101930 (Macros bound to HTML document events ran without a security check), 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-101930 (entry last updated 2026-11-16):
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 Writer opens the HTML document. (source: https://www.libreoffice.org/security/#cve-2026-101930)
- The HTML document binds macros to document-wide events such as being opened or closed. (source: https://www.libreoffice.org/security/#cve-2026-101930)
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-101930 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101930 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-101930
- https://www.libreoffice.org/security/#cve-2026-101930
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-101930
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-101930"}.

Timeline

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

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

Is CVE-2026-101930 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?

Macros bound to document-wide events in an HTML document, such as the document being opened or closed, could run when the document is opened, regardless of the macro security level.Source: libreoffice.org

Which versions are affected by CVE-2026-101930?

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-101930?

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