Ubuntu Fixes signing-party OpenPGP Key Command Injection
Tech GuruQuick Answer
Update signing-party before using gpg-key2ps on untrusted keys. Review automated key-printing and signing workflows.
Confirm Scope And Apply The Supported Remediation
What to do now: Inventory Ubuntu suite, installed signing-party packages, repository origin, active consumers and owners. Match the installed suite and package to the official notice; assess upstream or bundled copies separately. Install the listed security packages through the supported Ubuntu repositories. Confirm required Ubuntu Pro, ESM or Legacy Support entitlements for older suites. Verify the installed tool and exercise approved key-processing workflows; retain package and execution records.
Last verified: 2026-11-13 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | signing-party gpg-key2ps on the Ubuntu releases listed in USN-9087-1 |
|---|---|
| Advisory | USN-9087-1 |
| CVE | CVE-2019-11627 |
| Authoritative release date | 2026-11-12 — November 12, 2026 at 20:55:13 UTC, from the official Ubuntu security feed; the notice gives the same date. |
| Authority revision date | No separate revision date is provided by the authority. |
| Affected versions | Ubuntu signing-party packages on the suites listed in the fixed-version table, before their respective security updates. Applicability is package-, feature- and suite-specific. |
| Fixed version | 18.04 LTS: signing-party 2.7-1ubuntu0.1~esm1; 16.04 LTS: signing-party 2.2-1ubuntu0.1~esm1 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | The Ubuntu notice does not confirm exploitation in the wild.; no exploitation claim is inferred. |
What Changed
Unescaped OpenPGP user IDs can reach a shell when gpg-key2ps processes a crafted key.
What To Validate Now
- Inventory. Inventory Ubuntu suite, installed signing-party packages, repository origin, active consumers and owners.
- Establish applicability. Match the installed suite and package to the official notice; assess upstream or bundled copies separately.
- Remediate. Install the listed security packages through the supported Ubuntu repositories. Confirm required Ubuntu Pro, ESM or Legacy Support entitlements for older suites.
- Validate. Verify the installed tool and exercise approved key-processing workflows; retain package and execution records.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
A user must process a crafted key. Avoid running key-formatting tools with unnecessary privileges.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
