NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

OpenStack Keystone does not check signature TTL of the EC2 credential auth methodGHSA-rqw2-hhrf-7936

MEDIUM

GHSA-rqw2-hhrf-7936 is a medium-severity (CVSS 5.4) CWE-294 vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

Also known asCVE-2020-12692PYSEC-2020-56
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.00%0.40%0.80%1.21%0.1%0.7%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.

Affected Packages

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

Affected Products

2 products · 3 configurations
OS
ubuntu linuxcanonical
1 version
18.04
Application
keystoneopenstack
< 15.0.1
1 version
16.0.0

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 16.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rqw2-hhrf-7936 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.

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 HatModerate
ProductFixed inAdvisory
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. The EC2 API doesn't have a signature TTL check for AWS Signature V4. An attacker can sniff the Authorization header, and then use it to reissue an OpenStack token an unlimited number of times.
O3 Security · Impact-Aware SCA

Is GHSA-rqw2-hhrf-7936 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
OpenStack Keystone does not check signature TTL of the…