How severe is CVE-2019-19687?

CVE-2019-19687 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-19687?

CVE-2019-19687 affects the following packages: keystone (PyPI), keystone (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2019-19687?

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

How do I detect CVE-2019-19687 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 CVE-2019-19687 if there is no patch (or I can't update yet)?

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.

Is CVE-2019-19687 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2019-19687, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-19687?

CVE-2019-19687 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 CVE-2019-19687?

CVE-2019-19687 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-19687 published, and has it been updated?

CVE-2019-19687 was published on December 9, 2019 and was last updated on October 24, 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

HIGH severity

CVE-2019-19687 — keystone

HIGHFix: openstack/keystone@1794751

CVE-2019-19687 is a high-severity (CVSS 8.8) CWE-522 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 Keystone Credential Leakage

Also known asGHSA-2j23-fwqm-mgwrPYSEC-2019-29

Published

Dec 9, 2019

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 4, 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.

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

OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the list credentials API. Any user with a role on a project is able to list any credentials with the /v3/credentials API when enforce_scope is false. Users with a role on a project are able to view any other users' credentials, which could (for example) leak sign-on information for Time-based One Time Passwords (TOTP). Deployments with enforce_scope set to false are affected. (There will be a slight performance impact for the list credentials API once this issue is fixed.)

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`keystone`	≥ 15.0.0&&< 15.0.1	15.0.1`pip install --upgrade 'keystone==15.0.1'`
🐍PyPI	`keystone`	≥ 16.0.0&&< 16.0.1	16.0.1`pip install --upgrade 'keystone==16.0.1'`

Affected Products

1 product · 2 configurations

Application

keystoneopenstack

2 versions

15.0.016.0.0

Exploits & PoCs

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

OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in the …

bugs.launchpad.netNVDDec 2019

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 15.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-19687 is resolved across your whole dependency graph.
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 HatImportant

Workaround published by Red Hat

To mitigate this issue, set the [oslo_policy] enforce_scope option to 'true' in the keystone.conf file.

Source: Red Hat security advisory for CVE-2019-19687 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenStack Platform 15.0 (Stein)	`openstack-keystone-1:15.0.1-0.20190720060412.5f27c4b.1.el8ost`	RHSA-2019:4358
Red Hat OpenStack Platform 16.0 (Train)	`openstack-keystone-1:16.0.1-0.20191210095025.bd3f637.el8ost`	RHEA-2020:0283

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-19687 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works