On this page (7 sections)

On November 18, 2026, the Debian Security Team published DSA-6636-1, a security update for libvisio, a library that reads drawings in the Microsoft Visio VSD and VSDX formats. The advisory says missing input sanitising could result in denial of service or potentially the execution of arbitrary code, and it is tracked as CVE-2026-106535.

If you run Debian 13 (trixie) servers or workstations that process Visio files, for example document converters, preview generators, or office suites that link against libvisio, you should install the update. Debian's advisory is currently the only source we have, so several details below are marked as unconfirmed.

What happened

Debian's advisory states that libvisio did not sufficiently sanitise input. The advisory describes the result as denial of service or, potentially, execution of arbitrary code. It recommends upgrading libvisio packages and says that for the stable distribution (trixie) the problem is fixed in version 0.1.7-1+deb13u1.

The advisory is short. It does not include a CVSS score, a description of the exact code path, the upstream fix, or any report of attacks in the wild. We will not guess at those details.

What the weakness means in plain terms

Libraries that parse complex file formats receive data they cannot trust. If a parser does not check that values inside a file are sane before using them, a specially crafted file can make the program crash, which is the denial of service case. In worse cases the same kind of mistake can let an attacker influence what the program does, which is why Debian says code execution is possible. Debian uses the word potentially, so treat code execution as a risk to plan for, not a confirmed outcome.

The practical attack path for a parsing flaw of this kind is a malicious file reaching software that opens it. The advisory does not describe a specific delivery method, so the realistic exposure depends on how your systems handle Visio files.

Who is realistically exposed

  • Servers that convert, preview, or index uploaded documents and link against libvisio, such as document pipelines behind web applications.
  • Desktop or shared workstations running Debian trixie where office software opens Visio drawings received by email or download.
  • Mail gateways or file scanners that open attachments to inspect them, if they use libvisio through another package.
  • Debian releases other than trixie: the advisory only names trixie, so check the Debian security tracker for libvisio for the status of other releases.

If nothing on a machine ever opens VSD or VSDX files, the risk is lower, but the library may still be installed as a dependency of another package, so updating is the simplest route.

How to check your exposure

The first command shows whether libvisio packages are installed and which version you have. Run it on each Debian host. A version older than 0.1.7-1+deb13u1 on trixie means you still need the update.

List installed libvisio packages and versions (Debian)Shell
dpkg -l | grep -i libvisio

If a package shows up, this command lists which installed packages depend on it, which tells you what software could pass Visio files to it. Run it with the actual package name from the previous output.

Show packages that depend on a libvisio package (Debian; replace the name with the one found above)Shell
apt-cache rdepends --installed libvisio-0.1-1
The package name libvisio-0.1-1 is an example of a typical library package name. Use the exact name that dpkg reports on your system.

What to do now

  1. Run dpkg -l | grep -i libvisio on Debian hosts to find installed libvisio packages and note their versions.
  2. Refresh package lists and upgrade the libvisio packages to 0.1.7-1+deb13u1 on trixie, as recommended in DSA-6636-1.
  3. Restart long-running services that load the library, such as document conversion workers or office suite daemons, so they use the fixed version.
  4. Review which services accept Visio files from users or email, and consider blocking or isolating that processing until you have patched.
  5. Check the Debian security tracker for libvisio if you run a Debian release other than trixie.
  6. Subscribe to the debian-security-announce list or your distribution's update notifications so future advisories reach you quickly.

This pair of commands refreshes package metadata and upgrades only the libvisio package. Replace the package name with the one found earlier. The result should show the package moving to 0.1.7-1+deb13u1 on trixie.

Update a single package to the fixed version (Debian trixie; run as root or with sudo)Shell
sudo apt-get update
sudo apt-get install --only-upgrade libvisio-0.1-1

Afterwards, run the version check again to confirm the installed version.

Confirm the installed version after updating (Debian)Shell
dpkg -l | grep -i libvisio
Caution. Upgrading a shared library does not change programs that are already running; they keep the old code in memory until restarted. Schedule restarts of document-processing services carefully so you do not interrupt jobs in progress.
Tip. If you handle many hosts, use your existing configuration management or unattended-upgrades setup to roll out the fix, then verify versions centrally instead of host by host.

Detection and monitoring

The advisory reports no exploitation, and we have no indicators of compromise to share. Sensible monitoring is general good practice: watch for crashes or repeated restarts of services that process documents, since a denial of service attempt against a parser would typically look like that. Review application logs for unusual spikes in failed conversions of Visio files, and keep an eye on unexpected child processes spawned by document-handling services.

For public websites that accept document uploads, keep upload types restricted to what you need and process files in an isolated, low-privilege environment. Our guide to small business website security covers broader habits, and Webforta Scan can run read-only checks on websites you verify, although it does not inspect libraries installed on your servers.

What we do not know yet

  • No CVSS score or severity rating appears in the available source.
  • The advisory does not say whether the flaw is being exploited.
  • The technical root cause and the upstream fix are not described in the advisory.
  • Only one independent publisher, Debian itself, covers this story so far, so there is no second source to compare against.

We will treat this as a routine but worthwhile patch: the possible impact includes code execution, the fix is available, and applying it is low effort.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6636-1] libvisio security updatelists.debian.org ·
  • Debian
  • libvisio
  • CVE-2026-106535
  • DSA
  • patching