Skip to main content

CVE-2026-104933The Document Foundation LibreOffice incomplete denylist

Low priorityMedium6.7EPSS not scored yet

CVE-2026-104933 is a incomplete denylist in The Document Foundation LibreOffice, rated medium (6.7 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

A list of forbidden inputs misses some, so a variant gets through. The software reveals data to someone who should not see it.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker drive the component into behaviour its authors did not intend. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place The Document Foundation LibreOffice runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. Limit who can run code or sign in on the hosts that run it.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

LibreOffice can embed audio and video in documents. Where it plays media with GStreamer, as on Linux, the media is opened when the document is loaded, and a preview image of a video is shown in the document and in its exports, such as PDF. A crafted media file could make GStreamer read a local file and draw its text into the preview image, so that the content of the file ended up in an exported document. This is a different route to the problem fixed for CVE-2026-63269. In fixed versions GStreamer opens only media in a short list of common, self-contained container formats.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Interfaces that accept external input. The flaw sits at the input boundary of the affected component.
  • Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
  • APIs that over-share. The flaw sits between internal data and whoever can read the response or log.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.

Questions to answer about your own systems

  • Where does The Document Foundation LibreOffice run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.