How severe is GHSA-jwpw-ppj5-7h4w?

No CVSS score has been assigned to GHSA-jwpw-ppj5-7h4w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jwpw-ppj5-7h4w?

GHSA-jwpw-ppj5-7h4w affects the following packages: keystone (PyPI), keystone (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-jwpw-ppj5-7h4w?

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

How do I detect GHSA-jwpw-ppj5-7h4w 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-jwpw-ppj5-7h4w if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-jwpw-ppj5-7h4w actively exploited in the wild?

No public exploit code has been indexed for GHSA-jwpw-ppj5-7h4w 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-jwpw-ppj5-7h4w?

GHSA-jwpw-ppj5-7h4w has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th 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-jwpw-ppj5-7h4w?

GHSA-jwpw-ppj5-7h4w is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jwpw-ppj5-7h4w published, and has it been updated?

GHSA-jwpw-ppj5-7h4w was published on May 13, 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 Logs PasswordsGHSA-jwpw-ppj5-7h4w

GHSA-jwpw-ppj5-7h4w is a Information Exposure vulnerability in keystone. A fix is available for keystone — see the affected versions and patch details below.

Also known asCVE-2015-3646PYSEC-2026-655

Published

May 13, 2022

Updated

Jul 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

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

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

OpenStack Identity (Keystone) before 2014.1.5 and 2014.2.x before 2014.2.4 logs the backend_argument configuration option content, which allows remote authenticated users to obtain passwords and other sensitive backend information by reading the Keystone logs.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystone`	≥ 2011.3&&< 2014.1.5	2014.1.5`pip install --upgrade 'keystone==2014.1.5'`
🐍PyPI	`keystone`	≥ 2014.2&&< 2014.2.4	2014.2.4`pip install --upgrade 'keystone==2014.2.4'`

Affected Products

2 products · 3 configurations

Application

keystoneopenstack

≥ 2014.2.0 && < 2014.2.4

range

solarisoracle

1 version

11.2

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 2014.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jwpw-ppj5-7h4w is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-jwpw-ppj5-7h4w in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works