CVE-2026-40299: amannn next-intl · Open Redirect
Affects amannn next-intlSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.9.1 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.9.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade amannn next-intl to 4.9.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| amannnnext-intl | Affected
| Fixed in
|
npmnext-intlpkg:npm/next-intlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the next-intl package to version 4.9.1 or later, where this open redirect vulnerability has been patched. Since the vendor advisory indicates the problem has been fixed in version 4.9.1, applying this official fix is the recommended remediation. Patch status is confirmed by the vendor advisory statement.
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`.
References
- github.com/amannn/next-intl/security/advisories/GHSA-8f24-v5vv-gm5j (opens in a new tab)
- github.com/amannn/next-intl/pull/2304 (opens in a new tab)
- github.com/amannn/next-intl/commit/1c80b668aa6d853f470319eec10a3f61e78a70e6 (opens in a new tab)
- github.com/amannn/next-intl/releases/tag/v4.9.1 (opens in a new tab)