Nuxt versions 3.x and 4.0.0 up to but not including 4.6.4 expose the message and data of unhandled errors thrown during server rendering to clients. This occurs when errors not explicitly created as HTTP errors propagate to the error page, causing sensitive information such as internal error messages, upstream response bodies, or tokens in URLs to be included in the client-visible payload. The issue is fixed in Nuxt 4.6.4 by marking such errors as unhandled and returning generic messages instead. Nuxt 3 is end-of-life and will not receive a fix. Workarounds include catching and rethrowing errors with sanitized messages or using a Nitro plugin to hide error details. If secrets were exposed, rotation is recommended.