Skip to main content
CVE-2026-101930VulnerabilityPublished

LibreOffice Writer can open HTML documents, and an HTML document can bind macros to events of the document as a whole

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-101930· High 8.5

Not known to be exploited · CVSS 8.5 High.

Data as of 16 Nov 2026, 20:03 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Document Fdn.)CVSS 4.08.5
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
The Document FoundationLibreOfficeAffected
  • =26.2
  • =26.8
Fixed in–
Debiandebian/libreofficepkg:deb/debian/libreofficeOther threatsAffected
  • =26.2
  • =26.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Use fixed versions of LibreOffice Writer where macros bound to document-level events are subject to macro security checks like other macros. Until updated, exercise caution when opening HTML documents from untrusted sources.

Description

LibreOffice Writer versions prior to the fix allow HTML documents to bind macros to document-level events such as opening or closing. These macros were not properly checked by the macro security mechanism and could execute regardless of the macro security level set by the user. The issue is addressed in fixed versions where such macros are subject to the same security checks as other macros.

References

Community reviews

Loading reviews…