VDB

GHSA-pr6x-p264-jrpq

GHSA-pr6x-p264-jrpq PUBLISHED CVSS 4.699999809265137 MEDIUM

Record from GitHub Advisory Database · Published August 23, 2022

There is a flaw in RPM's signature functionality. OpenPGP subkeys are associated with a primary key via a "binding signature." RPM does not check the binding signature of subkeys prior to importing them. If an attacker is able to add or socially engineer another party to add a malicious subkey to a legitimate public key, RPM could wrongly trust a malicious signature. The greatest impact of this flaw is to data integrity. To exploit this flaw, an attacker must either compromise an RPM repository or convince an administrator to install an untrusted RPM or public key. It is strongly recommended to only use RPMs and public keys from trusted sources.

Risk scores

CVSS 3.1
4.699999809265137
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

Timeline

  • Aug 23, 2022 CVE Published
  • Apr 10, 2026 Distribution Patch (3 in total, the first dated here)
  • Apr 10, 2026 Security Advisory

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln GHSA-pr6x-p264-jrpq
vulnetix vdb fixes GHSA-pr6x-p264-jrpq

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/GHSA-pr6x-p264-jrpq/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›