Vulnerability Database · npm · next · Version
next 16.3.8
16.3.8 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 30 Sep 2026
Licence MIT
Also known from other sources 0
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
next 16.3.8 vulnerabilities
1 vulnerability cover next 16.3.8. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| GHSA-673q-mjm6-r5xr: Unauthenticated remote code execution in Next.js cache functions | 9.5 critical | 16.4.1 | 22 Oct 2026 |
Looking for another version, or everything Vulert holds for next?
Questions
About next 16.3.8
Is next 16.3.8 vulnerable?
Yes. 1 vulnerability in the Vulert database cover next 16.3.8: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 16.3.8 the latest release of next?
No. 16.3.8 was published 30 Sep 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor next for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the next version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.