Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8f24-v5vv-gm5j | next-intl has an open redirect vulnerability |
Mon, 20 Apr 2026 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 20 Apr 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Amannn
Amannn next-intl |
|
| Vendors & Products |
Amannn
Amannn next-intl |
Mon, 20 Apr 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 17 Apr 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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 `next-intl@4.9.1`. | |
| Title | next-intl has an open redirect vulnerability | |
| Weaknesses | CWE-601 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-20T15:58:51.149Z
Reserved: 2026-04-10T20:22:44.035Z
Link: CVE-2026-40299
Updated: 2026-04-20T15:56:13.622Z
Status : Deferred
Published: 2026-04-17T21:16:34.707
Modified: 2026-04-29T21:04:10.060
Link: CVE-2026-40299
OpenCVE Enrichment
Updated: 2026-04-20T14:59:37Z
Github GHSA