On this page (7 sections)
Ubuntu published USN-9087-1 on 12 November 2026. It covers signing-party, a package of OpenPGP related tools. Ubuntu says the gpg-key2ps tool did not properly sanitize user IDs before passing them to a shell, so processing a specially crafted OpenPGP key could let an attacker run programs as the login of the user who processed it.
This matters to administrators of Ubuntu 16.04 LTS and 18.04 LTS systems where signing-party is installed. According to the notice, the fixed packages are ESM packages available with Ubuntu Pro via ESM Apps, so check how your systems receive updates.
What happened
Ubuntu's notice describes a single weakness in one tool inside the signing-party package. The tool is gpg-key2ps. According to Ubuntu, it took user IDs from an OpenPGP key and passed them to a shell without sanitizing them first. A user ID is text stored in the key by whoever created it, so an attacker who crafts a key controls what it contains.
The notice says the attack requires that a user be tricked into processing a specially crafted key, and that the attacker could then possibly execute arbitrary commands. The overview says the programs would run as the victim's login. Ubuntu does not say whether the flaw has been exploited, and the research contains no severity score, so treat the urgency as unrated rather than low.
The weakness in plain terms
This is a command injection pattern. When a program builds a shell command by pasting in text it did not write, special characters in that text can end the intended command and start another. Safe code either avoids the shell entirely or strictly escapes the input.
The practical lesson is that a key you did not create is untrusted data, and its user ID can contain anything. Treat keys from outside sources with the same caution as any other file from an unknown party.
Who is realistically exposed
- Ubuntu 18.04 LTS and 16.04 LTS machines with the signing-party package installed. These are the two releases the notice lists.
- Users who run gpg-key2ps on a key that was crafted by an attacker. The notice says a user would need to be tricked into processing such a key. Merely having the package installed does not run the tool.
- Anyone processing keys, since the notice says the programs would run as the login of the user who processed the key.
Systems that do not have signing-party installed are not covered by this notice. Checking takes a few seconds per host, as shown below.
How to check your exposure
First, see whether the package is installed and which version you have. This is read-only. A line starting with ii means it is installed; compare the version with the fixed versions in the table below.
dpkg -l signing-party| Ubuntu release | Package | Fixed version |
|---|---|---|
| 18.04 LTS (bionic) | signing-party | 2.7-1ubuntu0.1~esm1 |
| 16.04 LTS (xenial) | signing-party | 2.2-1ubuntu0.1~esm1 |
Next, check whether the machine is attached to Ubuntu Pro, because the notice says the fix is available with Ubuntu Pro via ESM Apps. This command only reports status.
pro statusWhat to do now
- Run dpkg -l signing-party on each Ubuntu 16.04 and 18.04 host to find where it is installed.
- If it is not needed, plan to remove it. A tool you do not use is attack surface you do not need.
- If you need it, attach the machine to Ubuntu Pro (free for up to five machines, per Ubuntu) and enable ESM Apps.
- Update the package and confirm the version matches 2.7-1ubuntu0.1~esm1 (18.04) or 2.2-1ubuntu0.1~esm1 (16.04).
- Until patched, do not run gpg-key2ps on keys from untrusted or unknown sources.
- Keep a list of hosts on these older releases and decide whether to upgrade them.
Once the host has ESM Apps enabled, update only this package. Ubuntu says a standard system update will make the necessary changes; the command below limits the change to one package.
sudo apt update && sudo apt install --only-upgrade signing-partyDetection and monitoring
The research gives no indicators of compromise, so there is no specific log pattern to search for. As general practice, not drawn from the notice, review shell history and process logs of accounts that handle OpenPGP keys, and watch for unexpected child processes spawned when keys are processed.
More broadly, keep an inventory of which Ubuntu release each of your servers runs and which packages are installed. Outside-in checks such as Webforta Scan look at what a site exposes to the internet and cannot tell you whether a local tool like this is installed, so package inventory on the host remains your job. For wider habits, see our guide to small business website security.
Timeline
- 12 November 2026: Ubuntu publishes USN-9087-1 for Ubuntu 18.04 LTS and 16.04 LTS, referencing CVE-2019-11627.
- Ubuntu notes that a community fix might become publicly available in the future.
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.
