Findings

CVE-2026-107371

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 request…

Published Oct 13, 2026 · updated Oct 14, 2026

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.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 13, 2026 · Catalog

    Detected

    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.

  2. Oct 14, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgCVE-2026-107371

    Official CVE identifier

    cve.org
  • FIRST EPSSCVE-2026-107371

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDCVE-2026-107371

    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 olde

    nvd.nist.gov

References

CVE-2026-107371 · ZeroDay Findings