Vulnerability Description
next-intl provides internationalization for Next.js. Applications using the `next-intl` middleware prior to version 4.9.1with `localePrefix: 'as-needed'` could construct URLs where path handling and the WHATWG URL parser resolved a relative redirect target to another host (e.g. scheme-relative `//` or control characters stripped by the URL parser), so the middleware could redirect the browser off-site while the user still started from a trusted app URL. The problem has been patchedin `[email protected]`.
Related Weaknesses (CWE)
References
- https://github.com/amannn/next-intl/commit/1c80b668aa6d853f470319eec10a3f61e78a7
- https://github.com/amannn/next-intl/pull/2304
- https://github.com/amannn/next-intl/releases/tag/v4.9.1
- https://github.com/amannn/next-intl/security/advisories/GHSA-8f24-v5vv-gm5j
FAQ
What is CVE-2026-40299?
CVE-2026-40299 is a documented vulnerability. next-intl provides internationalization for Next.js. Applications using the `next-intl` middleware prior to version 4.9.1with `localePrefix: 'as-needed'` could construct URLs where path handling and t...
How severe is CVE-2026-40299?
CVSS scoring is not yet available for CVE-2026-40299. Check NVD for updates.
Is there a patch for CVE-2026-40299?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.