next-auth (npm) has 14 known vulnerabilities, the worst rated CRITICAL. Upgrade to 5.0.0-beta.32 or later to clear all of them. No malicious-package signal is recorded.
CyberXYZ does not call a package safe in absolute terms. It records 14 known vulnerabilities for next-auth (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does next-auth have known vulnerabilities?
Yes. CyberXYZ records 14 known vulnerabilities for next-auth (npm), the worst rated CRITICAL. These include GHSA-7rqj-j65f-68wh, GHSA-8fpg-xm3f-6cx3, GHSA-xv97-c62v-4587, GHSA-xmf8-cvqr-rfgj, GHSA-7r7x-4c4q-c4qf.
Which version of next-auth should I use?
5.0.0-beta.32 or later clears every advisory recorded for next-auth (npm). Check the release you pick before installing it.
How do I check next-auth before installing?
Search next-auth in CyberXYZ Check at https://cyberxyz.io/check?q=next-auth. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:23 UTC. The most recent advisory here was published 2026-07-23. Updated continuously from NVD, GHSA, OSV and CNA feeds.