Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

GHSA-4427-7f3w-mqv6 — keystone

HIGHFix: openstack/keystone@37e9907

GHSA-4427-7f3w-mqv6 is a high-severity (CVSS 8.8) CWE-863 vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

OpenStack Keystone V3 /credentials endpoint policy logic allows to change credentials owner or target project ID

Also known asCVE-2020-12691PYSEC-2020-55
Published
May 24, 2022
Updated
Sep 27, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 25, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-4427-7f3w-mqv6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected
🐍keystone🐍keystone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIkeystoneall versions15.0.1pip install --upgrade 'keystone==15.0.1'
🐍PyPIkeystone≥ 16.0.0&&< 16.0.116.0.1pip install --upgrade 'keystone==16.0.1'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for keystone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update keystone to 15.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4427-7f3w-mqv6 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4427-7f3w-mqv6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-4427-7f3w-mqv6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat Quay includes keystone-client, which is not vulnerable to this (server-side) vulnerability.

ProductFixed inAdvisory
Red Hat OpenStack Platform 10.0 (Newton)openstack-keystone-1:10.0.3-8.el7ostRHSA-2020:3096
Red Hat OpenStack Platform 13.0 (Queens)openstack-keystone-1:13.0.4-3.el7ostRHSA-2020:2732
Red Hat OpenStack Platform 15.0 (Stein)openstack-keystone-1:15.0.1-0.20200512110437.95b2bbe.el8ostRHSA-2020:3102
Red Hat OpenStack Platform 16.0 (Train)openstack-keystone-1:16.0.1-0.20200511063421.40cbb7b.el8ostRHSA-2020:3105

Frequently Asked Questions

An issue was discovered in OpenStack Keystone before 15.0.1, and 16.0.0. Any authenticated user can create an EC2 credential for themselves for a project that they have a specified role on, and then perform an update to the credential user and project, allowing them to masquerade as another user. This potentially allows a malicious user to act as the admin on a project another user has the admin role on, which can effectively grant that user global admin privileges.
O3 Security · Impact-Aware SCA

Is GHSA-4427-7f3w-mqv6 in your dependencies?

O3 Security finds GHSA-4427-7f3w-mqv6 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-4427-7f3w-mqv6: keystone (High 8.8) | O3 Security