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

CVE-2017-2673 — keystone

HIGHFix: openstack/keystone@05a129e

CVE-2017-2673 is a high-severity (CVSS 7.2) CWE-863 vulnerability in keystone. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for keystone — see the affected versions and patch details below.

OpenStack Identity service (keystone) Incorrect Authorization

Also known asGHSA-j36m-hv43-7w7mPYSEC-2018-152
Published
Updated
Affected
3 pkgs
Patched
2 / 3
Exploits
1 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.3%probability of exploitation in next 30 days
Lower Risk+0.20%
Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk
0.05%0.98%1.90%2.82%0.6%2.3%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

3 pkgs affected
🐍keystone🐍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 authorization-check flaw was discovered in federation configurations of the OpenStack Identity service (keystone). An authenticated federated user could request permissions to a project and unintentionally be granted all related roles including administrative roles.

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIkeystone≥ 9.0.0No fix
🐍PyPIkeystone≥ 10.0.0&&< 10.0.210.0.2pip install --upgrade 'keystone==10.0.2'
🐍PyPIkeystone≥ 11.0.0&&< 11.0.111.0.1pip install --upgrade 'keystone==11.0.1'

Affected Products

1 product · 2 configurations
Application
openstackredhat
2 versions
910
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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

    A fix is available for CVE-2017-2673; check the affected-versions list above or the advisory for the patched release of keystone, then make sure no transitive dependency still pins the vulnerable range.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 10.0 (Newton)openstack-keystone-1:10.0.1-3.el7ostRHSA-2017:1597
Red Hat OpenStack Platform 9.0 (Mitaka)openstack-keystone-1:9.3.0-2.el7ostRHSA-2017:1461

Frequently Asked Questions

An authorization-check flaw was discovered in federation configurations of the OpenStack Identity service (keystone). An authenticated federated user could request permissions to a project and unintentionally be granted all related roles including administrative roles.
O3 Security · Impact-Aware SCA

Is CVE-2017-2673 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2017-2673: keystone — Fixed in 10.0.2