How severe is GHSA-8833-qrvm-wc3h?

No CVSS score has been assigned to GHSA-8833-qrvm-wc3h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8833-qrvm-wc3h?

GHSA-8833-qrvm-wc3h affects the following packages: keystone (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-8833-qrvm-wc3h?

Update keystone to 8.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8833-qrvm-wc3h is resolved across your whole dependency graph.

How do I detect GHSA-8833-qrvm-wc3h in my PyPI dependencies?

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.

How do I mitigate GHSA-8833-qrvm-wc3h if there is no patch (or I can't update yet)?

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.

Is GHSA-8833-qrvm-wc3h actively exploited in the wild?

No public exploit code has been indexed for GHSA-8833-qrvm-wc3h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-8833-qrvm-wc3h?

GHSA-8833-qrvm-wc3h has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8833-qrvm-wc3h?

GHSA-8833-qrvm-wc3h is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8833-qrvm-wc3h published, and has it been updated?

GHSA-8833-qrvm-wc3h was published on May 5, 2022 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

OpenStack Keystone allows context-dependent attackers to bypass access restrictionsGHSA-8833-qrvm-wc3h

Fix: openstack/keystone@7402f5e

GHSA-8833-qrvm-wc3h is a Improper Authentication vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

Also known asCVE-2013-0282PYSEC-2026-652

Published

May 5, 2022

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐍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

OpenStack Keystone Grizzly before 2013.1, Folsom 2012.1.3 and earlier, and Essex does not properly check if the (1) user, (2) tenant, or (3) domain is enabled when using EC2-style authentication, which allows context-dependent attackers to bypass access restrictions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystone`	all versions	8.0.0a0`pip install --upgrade 'keystone==8.0.0a0'`

Affected Products

1 product · 5 configurations

Application

keystoneopenstack

≥ 2012.2 && ≤ 2012.2.4

1 version

2013.1

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update keystone to 8.0.0a0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8833-qrvm-wc3h is resolved across your whole dependency graph.
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

Product	Fixed in	Advisory
OpenStack Folsom for RHEL 6	`openstack-keystone-0:2012.2.3-3.el6ost`	RHSA-2013:0596

Ubuntu

USN-1730-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-8833-qrvm-wc3h in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works