CVE-2020-15125

What it is

In auth0 (npm package) versions before 2.27.1, a DenyList of specific keys that should be sanitized from the request object contained in the error object is used. The key for Authorization header is not sanitized and in certain cases the Authorization header value can be logged exposing a bearer token. You are affected by this vulnerability if you are using the auth0 npm package, and you are using a Machine to Machine application authorized to use Auth0's management API

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure.

Exploit odds

1.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-07-29 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:56 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.5% in the next 30 days (EPSS).
• Severity: 7.7 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-07-29 17:15 UTC

Last modified

2026-06-17 02:56 UTC

Exploit probability

1.5% · EPSS, next 30 days

Weakness

CWE-209

Record status

Modified

Affected

• auth0 auth0.js < 2.27.1

Attack profile CVSS 3.1 · 7.7

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-15125.md and follow it. Check whether this project is affected by CVE-2020-15125. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge