How severe is CVE-2020-10187?

CVE-2020-10187 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-10187?

CVE-2020-10187 affects the following packages: doorkeeper (RubyGems), doorkeeper (RubyGems), doorkeeper (RubyGems), doorkeeper (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2020-10187?

Update doorkeeper to 5.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10187 is resolved across your whole dependency graph.

How do I detect CVE-2020-10187 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for doorkeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-10187 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 CVE-2020-10187 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-10187 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 CVE-2020-10187?

CVE-2020-10187 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-2020-10187?

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

When was CVE-2020-10187 published, and has it been updated?

CVE-2020-10187 was published on May 4, 2020 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

HIGH severity

CVE-2020-10187 — doorkeeper

HIGHFix: doorkeeper-gem/doorkeeper@25d0380

CVE-2020-10187 is a high-severity (CVSS 7.5) CWE-862 vulnerability in doorkeeper. A fix is available for doorkeeper — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper

Also known asGHSA-j7vx-8mqj-cqp9

Published

May 4, 2020

Updated

Oct 20, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

4 pkgs affected

💎doorkeeper💎doorkeeper💎doorkeeper💎doorkeeper

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Information disclosure vulnerability. Allows an attacker to see all Doorkeeper::Application model attribute values (including secrets) using authorized applications controller if it's enabled (GET /oauth/authorized_applications.json).

Patches

These versions have the fix:

5.0.3
5.1.1
5.2.5
5.3.2

Workarounds

Patch Doorkeeper::Application model #as_json(options = {}) method and define only those attributes you want to expose.

Additional recommended hardening is to enable application secrets hashing (guide), available since Doorkeeper 5.1. This would render the exposed secret useless.

References

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`doorkeeper`	≥ 5.0.0&&< 5.0.3	5.0.3`bundle update doorkeeper --conservative`
💎RubyGems	`doorkeeper`	≥ 5.1.0&&< 5.1.1	5.1.1`bundle update doorkeeper --conservative`
💎RubyGems	`doorkeeper`	≥ 5.2.0&&< 5.2.5	5.2.5`bundle update doorkeeper --conservative`
💎RubyGems	`doorkeeper`	≥ 5.3.0&&< 5.3.2	5.3.2`bundle update doorkeeper --conservative`

Affected Products

1 product · 4 configurations

Application

doorkeeperdoorkeeper_project

≥ 5.3.0 && < 5.3.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for doorkeeper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update doorkeeper to 5.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-10187 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.

Frequently Asked Questions

### Impact Information disclosure vulnerability. Allows an attacker to see all `Doorkeeper::Application` model attribute values (including secrets) using authorized applications controller if it's enabled (GET /oauth/authorized_applications.json). ### Patches These versions have the fix: * 5.0.3 * 5.1.1 * 5.2.5 * 5.3.2 ### Workarounds Patch `Doorkeeper::Application` model `#as_json(options = {})` method and define only those attributes you want to expose. Additional recommended hardening is to enable application secrets hashing ([guide](https://doorkeeper.gitbook.io/guides/security/token-