On this page (7 sections)
Ubuntu has published USN-9089-1, a security notice for x11vnc, a VNC server that allows remote access to an existing X session. The notice says x11vnc created shared memory segments with insecure permissions, which a local attacker could possibly use to obtain sensitive information or modify screen contents.
If you run Ubuntu 20.04 LTS systems with x11vnc installed, this is worth a few minutes. The issue is described as local, so it matters most on machines where more than one person or service can log in.
What Ubuntu reported
According to Ubuntu, x11vnc created shared memory segments with insecure permissions. Ubuntu's overview describes the impact as exposing sensitive information to local users, and the details add that a local attacker could possibly modify screen contents too. The notice lists a single CVE, CVE-2020-29074.
Only one publisher, Ubuntu itself, is the source here. The notice does not give a severity rating, technical exploit details, or any report of attacks in the wild, so none of those can be confirmed from this story.
The weakness in plain terms
Shared memory is a region of memory that several processes on the same machine can read and write. Access to it is controlled by permission bits, much like file permissions. When a program creates a segment with permissions that are too open, other local accounts may be able to attach to it.
Ubuntu's wording is cautious ("could possibly"), and the attacker is described as local. The notice does not describe a remote attack path.
Who is realistically exposed
- Ubuntu 20.04 LTS (focal) systems with the x11vnc package installed.
- Shared machines where several people or low-privilege accounts can log in or run code, since the issue is local. This is general context, not a detail from the notice.
A single-user machine with no other local accounts has a much smaller exposure, though that is our general reading and not something Ubuntu states.
How to check whether you are affected
This read-only command lists the installed x11vnc package and its version on Ubuntu. If it reports that nothing matches, the package is not installed. If the version on 20.04 LTS is older than 0.9.16-3ubuntu0.1~esm2, you do not have the fix yet.
dpkg -l x11vncThis read-only command shows whether an x11vnc process is currently running, which tells you whether a restart will be needed after updating.
pgrep -a x11vncWhat to do now
Ubuntu's notice says the fix for 20.04 LTS is available with Ubuntu Pro via ESM Apps, and that a community fix might become publicly available in the future, with no date given. It describes Ubuntu Pro as free for up to five machines. For how to obtain the fixes, follow the "Learn more about how to get the fixes" guidance linked from the Ubuntu notice.
- Run the dpkg check above on each Ubuntu 20.04 LTS machine to find out where x11vnc is installed.
- If x11vnc is not needed on a machine, consider removing the package to cut your exposure.
- Get the fixed package, x11vnc 0.9.16-3ubuntu0.1~esm2, using Ubuntu Pro via ESM Apps as described in Ubuntu's notice.
- After the standard system update, restart x11vnc so all the changes take effect.
- Re-run dpkg -l x11vnc to confirm the installed version matches the fixed one.
Monitoring afterwards
- Track which hosts still run x11vnc and at what version, so a newly built 20.04 machine does not reintroduce the old package.
- Review who holds local accounts on hosts that run x11vnc, and remove stale ones.
Patching the host is what resolves this issue, and no external service replaces it. For general hardening beyond this notice, the small business website security guide is a good starting point.
Timeline
| Date | Event |
|---|---|
| 12 November 2026 | Ubuntu publishes USN-9089-1 for x11vnc on 20.04 LTS |
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.
