Skip to content
OpenAdvisories

Vendor

auth0

44 known vulnerabilities.

auth0 at a glance

Last 12 months
20
Critical · all time
4
Exploited · all time
0
Public exploit · all time
1
New vulnerabilities per month · last 12 months
0 3 5 December 2025: 4 vulnerabilities Dec 2025 January 2026: 0 vulnerabilities February 2026: 0 vulnerabilities March 2026: 0 vulnerabilities Mar April 2026: 2 vulnerabilities May 2026: 1 vulnerability June 2026: 0 vulnerabilities Jun July 2026: 0 vulnerabilities August 2026: 0 vulnerabilities September 2026: 5 vulnerabilities, 1 critical Sep October 2026: 4 vulnerabilities November 2026: 4 vulnerabilities
Show as table
MonthVulnerabilitiesCritical
Nov 202640
Oct 202640
Sep 202651
Aug 202600
Jul 202600
Jun 202600
May 202610
Apr 202620
Mar 202600
Feb 202600
Jan 202600
Dec 202540
Nov 202500
Oct 202510
Sep 202500
Aug 202500
Jul 202500
Jun 202521
May 202532
Apr 202510
Mar 202500
Feb 202500
Jan 202500
Dec 202400

44 results · Feed

  • Unscored —

    The Auth0 ASP.NET Core Authentication SDK incorrectly determines a session's OIDC Back-Channel Logout status, which may…

  • Unscored —

    The Management API client in the Auth0 Node.js SDK improperly neutralizes path parameters, allowing a request and its a…

  • Unscored —

    The auth0-ai-python FGA retriever does not distinguish between authorization checks under different users, relations, o…

  • Unscored —

    The auth0-ai-js FGA retriever does not distinguish between authorization checks under different conditions when filteri…

  • Medium 5.3

    Out-of-Range Timestamp Claim Handling in auth0/java-jwt

    The auth0/java-jwt library may terminate a thread if it receives a JWT with a timestamp claim (exp, nbf, iat) containing an out-of-range value. The condition occurs during token parsing, prior to signature verification. Repeated requests of this nature may le…

  • Medium 5.4

    Missing Verification of auth_time Claim in auth0.js

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

  • Medium 5.3

    Improper Request Handling for Active Directory Logins in auth0-lock

    When a username for an Active Directory connection is a domain without a local part, the auth0-lock library initiates the authentication transaction with a GET request instead of a POST request. As a result, user-submitted form data is appended to the URL as …

  • Medium 6.1

    Improper Validation of Post-Login Redirect URL in nextjs-auth0

    The auth0/nextjs-auth0 SDK validates that the returnTo parameter is a same-origin URL. The SDK then stores this value and, in a later step, reconstructs it for the post-authentication redirect. The reconstruction logic can produce a URL that browsers interpre…

  • Medium 6.5

    Auth0 Symfony: Bearer Token Accepted via URL Query Parameter in Auth0 Symfony SDK

    Auth0 Symfony is a Symfony SDK for Auth0 Authentication and Management APIs. From 5.0.0-BETA0 until 5.9.0, the Authorizer::authenticate() and Authorizer::supports() paths in the Authorizer security authenticator may accept OAuth 2.0 bearer access tokens from …

  • Medium 6.5

    Improper Cache Isolation in auth0/react-native-auth0 SDK Web Platform Credential Management

    The react-native-auth0 SDK's web platform implementation does not scope its in-memory token cache to individual user sessions when operating in a server-side rendering (SSR) environment where module state persists across HTTP requests. Under the listed precon…

  • High 7.8

    Local Privilege Escalation in Auth0 AD/LDAP Connector

    The Auth0 AD/LDAP Connector improperly processes a configuration value during service startup. This allows a low-privileged user on the host system to modify the connector's configuration. When the service restarts, the modified configuration can lead to code…

  • Critical 9.0

    Stored Cross-Site Scripting (XSS) in Auth0 AD/LDAP Connector

    The Auth0 AD/LDAP Connector is vulnerable to stored Cross-Site Scripting (XSS) issues due to improper HTML encoding of data in search results and updater log content displayed in the admin panel. An authenticated user with privileges to modify directory attri…

  • Medium 6.7

    Unauthenticated Localhost Admin Panel in Auth0 AD/LDAP Connector

    The administrative panel of the Auth0 AD/LDAP Connector (versions 6.5.0 and earlier) listens on the local loopback interface without requiring authentication. This allows a local, low-privileged user or process on the host system to access the panel's managem…

  • High 7.1

    Improper Permission Checking in Auth.js SDK

    Auth0.js is a client-side JavaScript library for Auth0. From 8.11.0 to 9.32.0, under specific preconditions, the Auth0.js SDK may improperly return user profile information using a valid access token when a specifically crafted invalid ID token is provided. T…

  • Medium 5.4

    Auth0 Next.js SDK has Improper Proxy Cache Lookup

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. In versions 4.12.0 through 4.17.1, simultaneous requests that trigger a nonce retry may cause the proxy cache fetcher to perform improper lookups for the token re…

  • High 8.2

    Auth0 PHP SDK Insufficient Entropy in Cookie Encryption

    Auth0-PHP is a PHP SDK for Auth0 Authentication and Management APIs. From version 8.0.0 to before version 8.19.0, in applications built with the Auth0 PHP SDK, cookies are encrypted with insufficient entropy, which may result in threat actors brute-forcing th…

  • Medium 6.8

    Auth0-PHP SDK has Improper Audience Validation

    Auth0-PHP is a PHP SDK for Auth0 Authentication and Management APIs. In applications built with the Auth0-PHP SDK, the audience validation in access tokens is performed improperly. Without proper validation, affected applications may accept ID tokens as Acces…

  • Medium 5.7

    Auth0 Next.js SDK has Improper Validation of Query Parameters

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions 4.9.0 through 4.12.1 contain an input-validation flaw in the returnTo parameter, which could allow attackers to inject unintended OAuth query parameters …

  • Medium 5.4

    Auth0 Next.js SDK has Improper Request Caching Lookup

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the req…

  • High 7.5
    CVE-2025-65945 Public exploit

    auth0/node-jws improper HMAC signature verification vulnerability

    auth0/node-jws is a JSON Web Signature implementation for Node.js. In versions 3.2.2 and earlier and version 4.0.0, auth0/node-jws has an improper signature verification vulnerability when using the HS256 algorithm under specific conditions. Applications are …

  • Low 3.3

    auth0-PHP: Improper File Type Handling in Bulk User Import

    auth0-PHP is an SDK for Auth0 Authentication and Management APIs. In versions 3.3.0 through 8.16.0, the Bulk User Import endpoint in applications built with the SDK does not validate the file-path wrapper or value. Without proper validation, affected applicat…

  • High 7.7

    NextJS-Auth0 SDK Vulnerable to CDN Caching of Session Cookies

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. In Auth0 Next.js SDK versions 4.0.1 through 4.6.0, `__session` cookies set by auth0.middleware may be cached by CDNs due to missing Cache-Control headers. Three p…

  • Critical 9.3

    Auth0-PHP SDK Deserialization of Untrusted Data vulnerability

    Auth0-PHP is a PHP SDK for Auth0 Authentication and Management APIs. Versions 8.0.0-BETA3 prior to 8.3.1 contain a vulnerability due to insecure deserialization of cookie data. If exploited, since SDKs process cookie content without prior authentication, a th…

  • Critical 9.1

    Brute Force Authentication Tags of CookieStore Sessions in Auth0-PHP SDK

    Auth0-PHP provides the PHP SDK for Auth0 Authentication and Management APIs. Starting in version 8.0.0-BETA1 and prior to version 8.14.0, session cookies of applications using the Auth0-PHP SDK configured with CookieStore have authentication tags that can be …

  • High 8.6

    passport-wsfed-saml2 Has SAML Authentication Bypass via Attribute Smuggling

    passport-wsfed-saml2 provides passport strategy for both WS-fed and SAML2 protocol. A vulnerability present starting in version 3.0.5 up to and including version 4.6.3 allows an attacker to impersonate any user during SAML authentication by tampering with a v…

  • Critical 9.3

    passport-wsfed-saml2 Has SAML Authentication Bypass via Signature Wrapping

    passport-wsfed-saml2 provides passport strategy for both WS-fed and SAML2 protocol. A vulnerability present starting in version 3.0.5 up to and including version 4.6.3 allows an attacker to impersonate any user during SAML authentication by crafting a SAMLRes…

  • Medium 4.9

    Auth0 NextJS SDK v4 Missing Session Invalidation

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions starting from 4.0.1 and prior to 4.5.1, do not invoke `.setExpirationTime` when generating a JWE token for the session. As a result, the JWE does not con…

  • Medium 6.1

    Login by Auth0 <= 4.6.0 - Reflected Cross-Site Scripting via wle

    The Login by Auth0 plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the ‘wle’ parameter in all versions up to, and including, 4.6.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated …

  • Medium 5.9

    jsonwebtoken unrestricted key type could lead to legacy keys usage

    Versions `<=8.5.1` of `jsonwebtoken` library could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm. You are affected if you are using an algorithm and a key …

  • Medium 6.4

    jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()

    In versions `<=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify…

  • Medium 5.0

    jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC

    jsonwebtoken is an implementation of JSON Web Tokens. Versions `<= 8.5.1` of `jsonwebtoken` library can be misconfigured so that passing a poorly implemented key retrieval function referring to the `secretOrPublicKey` argument from the readme link will result…

  • Medium 5.3

    Passport-wsfed-saml2 vulnerable to Authentication Bypass for WSFed authentication

    Passport-wsfed-saml2 is a ws-federation protocol and SAML2 tokens authentication provider for Passport. In versions prior to 4.6.3, a remote attacker may be able to bypass WSFed authentication on a website using passport-wsfed-saml2. A successful attack requi…

  • Medium 6.1

    HTML injection with additional signup fields

    Auth0 is an authentication broker that supports both social and enterprise identity providers, including Active Directory, LDAP, Google Apps, and Salesforce. In versions before `11.33.0`, when the “additional signup fields” feature [is configured](https://git…

  • High 7.5

    Open Redirect in express-openid-connect

    Express OpenID Connect is an Express JS middleware implementing sign on for Express web apps using OpenID Connect. Users of the `requiresAuth` middleware, either directly or through the default `authRequired` option, are vulnerable to an Open Redirect when th…

  • Medium 6.4

    Open redirect in nextjs-auth0

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions before 1.6.2 do not filter out certain returnTo parameter values from the login url, which expose the application to an open redirect vulnerability. User…

  • Medium 4.6

    Session fixation in express-openid-connect

    Express OpenID Connect is express JS middleware implementing sign on for Express web apps using OpenID Connect. Versions before and including `2.5.1` do not regenerate the session id and session cookie when user logs in. This behavior opens up the application…

  • High 8.0

    Reflected XSS from the callback handler's error query parameter

    The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. Versions before and including `1.4.1` are vulnerable to reflected XSS. An attacker can execute arbitrary code by providing an XSS payload in the `error` query par…

  • High 8.1

    Reflected XSS when using flashMessages

    auth0-lock is Auth0's signin solution. Versions of nauth0-lock before and including `11.30.0` are vulnerable to reflected XSS. An attacker can execute arbitrary code when the library's `flashMessage` feature is utilized and user input or data from URL paramet…

  • High 8.1

    CSRF in Auth0 ad-ldap-connector

    ad-ldap-connector's admin panel before version 5.0.13 does not provide csrf protection, which when exploited may result in remote code execution or confidential data loss. CSRF exploits may occur if the user visits a malicious page containing CSRF payload on …

  • High 7.4

    Regression in JWT Signature Validation

    omniauth-auth0 (rubygems) versions >= 2.3.0 and < 2.4.1 improperly validate the JWT token signature when using the `jwt_validator.verify` method. Improper validation of the JWT token signature can allow an attacker to bypass authentication and authorization. …