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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8f24-v5vv-gm5j?

O3 pinpoints whether GHSA-8f24-v5vv-gm5j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 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

GHSA-8f24-v5vv-gm5j

GHSA-8f24-v5vv-gm5j is a Open Redirect vulnerability in next-intl. O3 Security confirms whether GHSA-8f24-v5vv-gm5j is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

next-intl has an open redirect vulnerability

Also known asCVE-2026-40299

Published

Apr 10, 2026

Updated

May 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

next-intlnpm

4.9Mdownloads / 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

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8f24-v5vv-gm5j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8f24-v5vv-gm5j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

O3 Security · Impact-Aware SCA

Is GHSA-8f24-v5vv-gm5j in your dependencies?

O3 detects GHSA-8f24-v5vv-gm5j across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works