CVE-2019-11627: gpg-key2ps in signing-party 1.1.x and 2.x before 2.10-1 contains an unsafe shell call enabling shell injection

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2019-11627 is a critical-severity flaw (CVSS 9.8) affecting signing-party, debian linux, leap. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

gpg-key2ps in signing-party 1.1.x and 2.x before 2.10-1 contains an unsafe shell call enabling shell injection via a User ID.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.7% (top 14%)
CISA exploited list	No
Weakness	CWE-78
Published	2019-04-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: debian · opensuse · signing-party project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-04-30 23:29 UTCPublished CVE record published
2026-06-17 02:13 UTCUpdated Record last modified

signing-party project signing-party UPGRADE

Affected: >= 1.1 and < 2.10

Fixed in: 2.10

Safe to downgrade to: a release before 1.1

1. Check installed version

apt-cache policy signing-party || rpm -q signing-party || signing-party --version

2. UPGRADE to 2.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade signing-party

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade signing-party

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.1 (Debian / Ubuntu)

apt-cache madison signing-party sudo apt install signing-party=<VERSION_BEFORE_1.1> sudo apt-mark hold signing-party

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list signing-party sudo dnf downgrade signing-party-<VERSION_BEFORE_1.1> sudo dnf versionlock add signing-party

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

debian debian linux MITIGATE

Affected: 8.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

opensuse leap MITIGATE

Affected: 15.0 · 42.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 15.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.

Fedora ELN · python-discovery · FIXED · 1.9.0-1.eln159 · FEDORA-2026-7a881c0c99 · source

sudo dnf upgrade --advisory=FEDORA-2026-7a881c0c99

Fedora 46 · pipx · FIXED · 1.18.11-1.fc46 · FEDORA-2026-443a765287 · source

sudo dnf upgrade --advisory=FEDORA-2026-443a765287

Ubuntu 20.04 · signing-party · NOT AFFECTED

Ubuntu 22.04 · signing-party · NOT AFFECTED

Ubuntu 24.04 · signing-party · NOT AFFECTED

Ubuntu 24.10 · signing-party · NOT AFFECTED

Ubuntu 25.04 · signing-party · NOT AFFECTED

Debian 12 · signing-party · FIXED · 2.10-1

sudo apt update && sudo apt install --only-upgrade signing-party dpkg --compare-versions "$(dpkg-query -W -f='${Version}' signing-party)" ge "2.10-1" && echo PATCHED || echo STILL-VULNERABLE

Debian 13 · signing-party · FIXED · 2.10-1

sudo apt update && sudo apt install --only-upgrade signing-party dpkg --compare-versions "$(dpkg-query -W -f='${Version}' signing-party)" ge "2.10-1" && echo PATCHED || echo STILL-VULNERABLE

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-11627?

signing-party: upgrade to 2.10; debian linux: mitigate or apply the listed mitigation; leap: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-11627 being exploited?

CVE-2019-11627 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-11627 affect?

CVE-2019-11627 affects signing-party, debian linux, leap. Severity is critical (CVSS 9.8). gpg-key2ps in signing-party 1.1.x and 2.x before 2.10-1 contains an unsafe shell call enabling shell injection via a User ID.

How urgent is CVE-2019-11627?

Priority 71/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Debian vulnerabilities

References

← Back to latest CVEs