Repository navigation
Guidance on bundled Undici and Zod versions in Next.js 16.4.3 #100864
Replies: 7 comments
|
Here is the technical context and guidance addressing each point for your security review: 1. Are these bundled versions intentionally maintained by Next.js?Yes. Next.js pre-compiles internal dependencies into its distribution packages (
2. Do known security advisories affecting standalone Undici or Zod apply here?No.
3. Is their relevant functionality reachable in a normal self-hosted production application?
4. Is a supported update or mitigation recommended?No remediation is needed.
5. Documentation to reference for internal security assessments
|
|
I wouldn't use the earlier reply's blanket “no remediation is needed” conclusion as evidence for your assessment. There is a concrete counterexample to the claim that Undici advisories only involve low-level dispatcher APIs: GHSA-c76h-2ccp-4975 / CVE-2025-22150 concerns multipart boundaries generated with I checked the published That file identifies Undici 6.21.0 and retains the That establishes that this advisory's code pattern is present in that bundled copy. It does not establish that your application exercises it under the advisory's conditions. Next has separate Node.js and Edge runtimes; finding the Edge primitives bundle in the archive does not prove that ordinary Node-runtime fetches use that copy. For the assessment, I'd record each advisory separately with:
For Zod, start with a specific advisory before drawing either conclusion. Its version number alone is insufficient, and the thread hasn't identified an applicable Zod advisory. Updating a separately installed |
|
Here is the architectural and security assessment regarding the bundled dependencies in Next.js 16.4.3:
|
|
One important distinction for the security assessment is the difference between a vulnerable dependency being present in the production archive and the application actually reaching the affected code path. For the Undici finding, have you confirmed whether your Azure deployment uses the Edge runtime or Node.js runtime for the affected requests? It would also be useful to verify whether the multipart request conditions described in CVE-2025-22150 are possible in your application. For Zod, I would first identify a specific advisory affecting 3.25.76 before deciding whether remediation is necessary. I would document the runtime, affected operation, and exploitability prerequisites separately rather than classifying either dependency as safe or vulnerable based only on its version. |
|
Those are vendored copies, not packages your app resolves from For a security review I would separate "present in the archive" from "reachable in your app". Grep the built output for imports of — |
|
Hi! I think the safest approach is to separate dependency presence from actual runtime exploitability. For the security review, I'd recommend checking:
For Undici, GHSA-c76h-2ccp-4975 is worth evaluating because its affected version range includes 6.21.0: For Zod, I would first identify a specific applicable advisory before determining whether remediation is required. I wouldn't classify the bundled dependencies as either safe or exploitable without validating their actual use in the production environment. |
|
Hey there! For Undici 6.21.0, there are published advisories affecting that version. The important question is whether Next.js 16.4.3 actually invokes the affected functionality in its production runtime. I'd approach the assessment by checking:
For Zod, I'd apply the same reasoning rather than assuming its internal validation usage is automatically safe or unsafe. I wouldn't recommend replacing files under For a production security review, I'd document the specific advisory, affected code path, reachability assessment, and mitigation separately for each finding. It would be helpful if the Next.js maintainers could confirm whether these bundled versions are intentional, which affected paths are reachable in production, and whether a supported dependency update is planned. |
Uh oh!
There was an error while loading. Please reload this page.
Summary
We are developing a self-hosted Next.js application deployed through Microsoft Azure.
During a pre-deployment security review, we identified the following bundled dependency versions in the Next.js 16.4.3 Linux production package:
Undici 6.21.0
Zod 3.25.76
We have confirmed that these versions are present in the production archive. However, we have not established an exploitable vulnerability or identified a specific applicable security advisory for these bundled copies.
We would appreciate guidance on:
1.Whether these bundled versions are intentionally maintained by Next.js.
2.Whether any known security advisories affecting these versions apply to their use within Next.js 16.4.3.
3.Whether their relevant functionality is reachable in a normal self-hosted production application.
4.Whether a supported update or mitigation is recommended.
5.Whether there is documentation we can reference in our internal dependency-security assessment.
Our goal is to establish whether a remediation is required, rather than assume that the presence of an older bundled version automatically constitutes a vulnerability.
Thank you for your assistance.
Additional information
No response
Example
No response
All reactions