Description
When the authorize() method is called with a maxAge parameter, the auth0.js library does not validate the auth_time claim in the resulting ID token against the requested maxAge value. As a result, an application may process an ID token that represents an authentication event older than the requested maximum age.
Published: 2026-10-13
Score: 5.4 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Authentication Time Validation Bypass
Action: Apply Patch
AI Analysis

Impact

The vulnerability allows auth0.js to accept an ID token whose authentication time is older than the maximum age requested by the application. This occurs because the authorize() method, when called with a maxAge parameter, fails to verify the auth_time claim in the resulting token, letting a stale authentication event be treated as fresh.

Affected Systems

Auth0’s auth0.js library, specifically versions older than 10.3.0, is impacted. Upgrading to version 10.3.0 or newer removes the bug. No other vendors or products are listed as affected.

Risk and Exploitability

The CVSS score of 5.4 marks this as moderate severity, while the EPSS score of less than 1 % indicates a low likelihood of exploitation. The vulnerability is not included in the CISA KEV catalog. The attack surface is limited to applications that rely on the vulnerable auth0.js library; an attacker would need to obtain or craft a stale ID token and rely on an application that does not enforce auth_time verification. Because the flaw is a missing validation rather than an injection or remote code execution, the impact is restricted to authentication freshness rather than a full system compromise.

Generated by OpenCVE AI on October 16, 2026 at 04:30 UTC.

Remediation

Vendor Solution

Upgrade auth0.js to version 10.3.0 or greater.


OpenCVE Recommended Actions

  • Upgrade the Auth0 auth0.js library to version 10.3.0 or newer
  • Configure your application to enforce auth_time verification when maxAge is requested, ensuring that stale ID tokens are rejected
  • Implement monitoring to detect abnormal authentication times and alert security teams

Generated by OpenCVE AI on October 16, 2026 at 04:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 17 Oct 2026 06:45:00 +0000

Type Values Removed Values Added
First Time appeared Auth0
Auth0 auth0.js
Vendors & Products Auth0
Auth0 auth0.js

Wed, 14 Oct 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 13 Oct 2026 20:30:00 +0000

Type Values Removed Values Added
Description When the authorize() method is called with a maxAge parameter, the auth0.js library does not validate the auth_time claim in the resulting ID token against the requested maxAge value. As a result, an application may process an ID token that represents an authentication event older than the requested maximum age.
Title Missing Verification of auth_time Claim in auth0.js
Weaknesses CWE-613
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Okta

Published:

Updated: 2026-10-14T18:40:31.506Z

Reserved: 2026-10-07T20:59:27.478Z

Link: CVE-2026-107371

cve-icon Vulnrichment

Updated: 2026-10-14T18:40:21.404Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-13T21:17:32.317

Modified: 2026-10-15T20:38:04.303

Link: CVE-2026-107371

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-17T06:30:05Z

Weaknesses
  • CWE-613

    Insufficient Session Expiration