On this page (7 sections)

Ubuntu has published USN-9088-1, dated 12 November 2026, for a TigerVNC flaw on Ubuntu 18.04 LTS. The TigerVNC viewer stored TLS certificate exceptions as trusted certificate authorities, which could let a remote attacker impersonate any VNC server after a user had accepted an exception for the attacker's server.

If you or your team use the TigerVNC viewer to reach servers, hosts or remote desktops from an Ubuntu 18.04 machine, this one is worth a few minutes. The notice rates the impact as exposure of sensitive information over the network. It does not give a severity score. Note that the fixed packages for 18.04 are available only through Ubuntu Pro (ESM Apps).

What the notice says

According to Ubuntu, the TigerVNC viewer stored TLS certificate exceptions as trusted certificate authorities. A remote attacker could possibly use this to impersonate any VNC server after a user had added a certificate exception for the attacker's server. Ubuntu summarizes the result as TigerVNC being made to expose sensitive information over the network.

The notice references CVE-2020-26117 and lists a related earlier notice, USN-5965-1. The research available for this story is a single primary source, the Ubuntu notice itself, so there is no independent analysis, proof of concept or exploitation report to draw on.

Why saved certificate exceptions are risky

VNC servers often use self-signed certificates. When a viewer cannot verify one, it asks the user whether to accept it anyway. That choice should apply only to that one server's certificate.

The flaw described by Ubuntu is that the viewer recorded the exception as a trusted certificate authority instead. A certificate authority is trusted to vouch for other certificates, so trusting one broadly is much more powerful than trusting a single server. In the notice's wording, an attacker could then impersonate any VNC server, not just the one the user approved.

The practical consequence of impersonating a remote desktop server is that a user could connect to the attacker's machine believing it is their own. Anything typed into that session, such as passwords, could be exposed. The notice itself only says sensitive information could be exposed; the password example is our illustration of what that can mean.

The attack described requires that a user first added a certificate exception for the attacker's server. Users who have never clicked through a certificate warning in the viewer have a smaller exposure, though the notice does not say how the stored exceptions are persisted, so do not assume you are unaffected without checking the package version.

Who is affected

The notice covers Ubuntu 18.04 LTS (bionic) only. The affected packages are all part of the tigervnc source package:

  • tigervnc-common
  • tigervnc-scraping-server
  • tigervnc-standalone-server
  • tigervnc-viewer
  • tigervnc-xorg-extension

The flaw is in the viewer, so the people most likely to matter are administrators and developers who connect out to VNC servers from 18.04 workstations or jump hosts. The notice does not say whether other Ubuntu releases or other distributions are affected, so check your own vendor's advisories for those.

How to check your exposure

Run this on an Ubuntu 18.04 machine to list installed TigerVNC packages and their versions. A version ending in 1.7.0+dfsg-8ubuntu2+esm1 or later means the fixed build is installed.

List installed TigerVNC packages and versions (Ubuntu 18.04)Shell
dpkg -l | grep -i tigervnc

To see which version your configured sources would install, and whether the ESM Apps repository is providing it, run the following. Look at the candidate version in the output.

Show installed and candidate version of the viewer (Ubuntu 18.04)Shell
apt-cache policy tigervnc-viewer

To see whether Ubuntu Pro is attached to the machine, run the status command below. The fix is delivered through ESM Apps, so it should be listed as enabled. If it is not, the fixed packages will not be offered to this machine.

Check Ubuntu Pro status and enabled servicesShell
pro status

What to do now

For Ubuntu 18.04, the notice says the fixed packages are available with Ubuntu Pro via ESM Apps, and that a community fix might become publicly available in the future. In other words, the fix is obtainable only once Ubuntu Pro is attached and ESM Apps is enabled on the machine; after that, Ubuntu says a standard system update makes the necessary changes. Ubuntu states Pro is free for up to five machines.

  1. Inventory Ubuntu 18.04 systems that have any tigervnc package installed.
  2. Attach Ubuntu Pro and enable ESM Apps on those machines if it is not already active; without it the fixed packages are not available.
  3. Once ESM Apps is enabled, run a standard update and confirm the TigerVNC packages are at 1.7.0+dfsg-8ubuntu2+esm1 or later.
  4. Ask users of the TigerVNC viewer to review servers they previously accepted certificate exceptions for, and to only connect to servers they recognize.
  5. Where possible, replace self-signed VNC certificates with certificates you control and distribute properly, so users are not trained to click through warnings.
  6. If a machine cannot be updated, consider limiting which hosts the viewer is used against until it can be.

After Ubuntu Pro with ESM Apps is enabled, this command refreshes package lists and upgrades only the TigerVNC viewer package on Ubuntu 18.04. Afterward, re-run the version check above.

Update the TigerVNC viewer package (Ubuntu 18.04 with ESM Apps enabled)Shell
sudo apt update && sudo apt install --only-upgrade tigervnc-viewer
Tip. If you run the standalone server or other TigerVNC packages on the same host, upgrade those too. The notice lists the same fixed version for all five packages, but they are offered only when ESM Apps is enabled, so confirm with the version check afterward rather than assuming a general upgrade covered them.

Monitoring and longer-term hygiene

Remote desktop access is a sensitive path into your systems, so it is worth treating certificate handling as part of your routine. Keep an inventory of which hosts expose VNC and which certificates they present, and renew or replace them before they expire. A certificate expiry and change monitor, such as Webforta Monitor, can alert you when certificates on your public hosts change unexpectedly, and the free SSL checker lets you inspect what a public endpoint presents.

As a general practice, avoid exposing VNC directly to the internet. Place it behind a VPN or an SSH tunnel, and treat any certificate warning on a server you manage as something to investigate rather than dismiss. For broader context on keeping small environments tidy, see our small business website security guide.

What we do not know

The Ubuntu notice does not include a severity rating or CVSS score, does not say whether the issue is being exploited, and does not describe how the stored exceptions are persisted. The CVE record data was not available in the research for this story, so we have not stated any score or attack vector beyond what Ubuntu wrote. We will treat any further detail as unconfirmed until a primary source provides it.

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. USN-9088-1: TigerVNC vulnerability | Ubuntu security notices | Ubuntuubuntu.com ·
  • TigerVNC
  • Ubuntu
  • USN
  • VNC
  • TLS certificates
  • Ubuntu Pro