next-auth npm Package Configuration Error: Potential Authentication Bypass
An early warning has been issued regarding a configuration error in the next-auth npm package that could potentially allow unauthenticated access. Users of affected versions are advised to review and correct their configurations.
What happened
Reportedly, a configuration error in the next-auth npm package can cause existence-based authentication checks to fail open, potentially allowing unauthenticated access. This issue arises when the auth object is populated with an error object instead of being null. The error is under investigation and the specific versions affected are detailed in the primary sources. It is recommended that users review and correct the configuration of the next-auth package to prevent unauthorized access.
The affected versions of next-auth include multiple ranges, as detailed in the primary sources. Users should consult the GitHub Advisory Database for the exact version ranges and fixed versions. The severity of this issue is considered high due to the potential for unauthorized access. Professional software engineers are advised to assess their exposure by checking their next-auth package configurations and updating to the fixed versions where applicable.
How 0Day mitigates this
next-auth is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.