next-intl (npm) has 2 known vulnerabilities, the worst rated MODERATE. Upgrade to 4.9.2 or later to clear all of them. No malicious-package signal is recorded.
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days
CyberXYZ composite out of 10
fig. 01 — GHSA-4c35-wcg5-mm9h, the advisory selected below
setNestedProperty in packages/next-intl/src/extractor/utils.tsx walks a dotted key path and assigns the final value without blocking the reserved keys proto…
Full advisory text at GitHub advisory.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
CyberXYZ does not call a package safe in absolute terms. It records 2 known vulnerabilities for next-intl (npm), the worst rated MODERATE, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 2 known vulnerabilities for next-intl (npm), the worst rated MODERATE. They are GHSA-4c35-wcg5-mm9h, GHSA-8f24-v5vv-gm5j.
4.9.2 or later clears every advisory recorded for next-intl (npm). Check the release you pick before installing it.
Search next-intl in CyberXYZ Check at https://cyberxyz.io/check?q=next-intl. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:00 UTC. The most recent advisory here was published 2026-05-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.