How severe is GHSA-8f24-v5vv-gm5j?

No CVSS score has been assigned to GHSA-8f24-v5vv-gm5j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8f24-v5vv-gm5j?

GHSA-8f24-v5vv-gm5j affects the following packages: next-intl (npm). Ecosystems affected: npm.

How do I fix GHSA-8f24-v5vv-gm5j?

Update next-intl to 4.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8f24-v5vv-gm5j is resolved across your whole dependency graph.

How do I detect GHSA-8f24-v5vv-gm5j in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next-intl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8f24-v5vv-gm5j if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is GHSA-8f24-v5vv-gm5j actively exploited in the wild?

No public exploit code has been indexed for GHSA-8f24-v5vv-gm5j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-8f24-v5vv-gm5j?

GHSA-8f24-v5vv-gm5j has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8f24-v5vv-gm5j?

GHSA-8f24-v5vv-gm5j is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8f24-v5vv-gm5j published, and has it been updated?

GHSA-8f24-v5vv-gm5j was published on April 10, 2026 and was last updated on May 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

next-intl has an open redirect vulnerabilityGHSA-8f24-v5vv-gm5j

Fix: amannn/next-intl#2304

GHSA-8f24-v5vv-gm5j is a Open Redirect vulnerability in next-intl. A fix is available for next-intl — see the affected versions and patch details below.

Also known asCVE-2026-40299

Published

Apr 10, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8f24-v5vv-gm5j.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

179other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

next-intlnpm

9.6Mdownloads / week

Description

Impact

Applications using the next-intl middleware with 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.

Patches

The problem has been patched, please update to [email protected].

Credits

Many thanks to Joni Liljeblad from Oura for responsibly disclosing the vulnerability and for suggesting the fix.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`next-intl`	all versions	4.9.1`npm install next-intl@4.9.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next-intl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next-intl to 4.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8f24-v5vv-gm5j is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

### Impact Applications using the `next-intl` middleware with `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. ### Patches The problem has been patched, please update to [`[email protected]`](https://github.com/amannn/next-intl/releases/tag/v4.9.1). ### Credits Many thanks to [Joni Liljeblad](https://github.com/j