Quick answers
- Is CVE-2026-107371 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107371 being exploited in the wild.
- How severe is CVE-2026-107371?
- Medium severity, with a CVSS score of 5.4, published 13 October 2026.
- Which products and versions are affected?
- Auth0.Js 9.12.0 through 10.2.1.
- Is there a fix for CVE-2026-107371?
- Yes: fixed in 10.3.0 or greater. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107371 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107371?
- Check whether you run Auth0.Js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 10.3.0 or greater
Technical details
The authorize() method does not validate the auth_time claim in ID tokens against the requested maxAge parameter, allowing authentication events older than the maximum age to be accepted. This is a missing claim validation issue (CWE-613) that requires the application to explicitly pass a maxAge value and the user's existing authentication to exceed that threshold. An attacker with the ability to reuse old session credentials can bypass freshness checks.
Affected products
- Auth0 auth0.js 9.12.0 through 10.2.1
Timeline
- 2026-10-13: disclosed