Skip to content

[miniflare] Update pinned Undici to 7.30.2 #16923

Open

Description

@Koslun

TL;DR

Bump Miniflare to Undici 7.30.2 for six security fixes.

Current published pins

wrangler@4.162.0 depends on miniflare@5.20261113.0-beta, which pins undici@7.30.1. The shared catalog on main also pins undici and undici-types to 7.30.1. The standalone miniflare@latest tag points to 4.20260730.0, which pins undici@7.28.0. Workers SDK catalog

Reproduction

These npm registry queries work on any operating system and require no project setup.

npm view wrangler@4.162.0 dependencies.miniflare
npm view miniflare@5.20261113.0-beta dependencies.undici
npm view miniflare@4.20260730.0 dependencies.undici

Requested update

Could you bump the shared undici and undici-types pins to 7.30.2 and publish the affected packages? We have not verified whether Miniflare uses the affected Undici features. Shipping the patch release however regardless saves each downstream consumer from having to assess the same advisories or override the pin.

Is there a target release for the bump, and is a backport planned for the Miniflare 4.x line on latest? I can prepare the catalog change, regenerated lockfile, and patch changeset if a maintainer would welcome a PR. Previous dependency update request

CVEs fixed in Undici 7.30.2

All six advisory version ranges include Undici 7.30.1. Five also include 7.28.0. Undici 7.30.2 release

  • CVE-2026-116592. Cache poisoning or cross-user disclosure via intermediate redirect hops. Upstream advisory
  • CVE-2026-120474. Cross-user disclosure when shared caching stores a credential-dependent redirect response. Upstream advisory
  • CVE-2026-116630. Cross-user disclosure via cross-origin redirects during cache revalidation. Upstream advisory
  • CVE-2026-120415. Credential leakage on cross-origin redirects when headers are supplied as name/value pairs. Upstream advisory
  • CVE-2026-120222. Denial of service from unhandled errors during cache replay. Upstream advisory
  • CVE-2026-120423. Subresource Integrity bypass via whitespace in integrity metadata. Upstream advisory

Activity

  1. workers-devprod commented on Nov 13, 2026

    @workers-devprod
    Contributor

    Automated triage

    Issue assessment

    • Actionability: ✅ Actionable.
    • Type: Task.
    • Reproduction: Skipped automatically.
    • Labels:
      • dependencies (high)
      • package:miniflare (high)
      • package:wrangler (medium)
      • maintenance (medium)
    Actionability and missing information

    Dependency update request: bump shared undici and undici-types pins from 7.30.1 to 7.30.2 in the pnpm catalog and publish affected miniflare and wrangler packages; reporter supplies current pin evidence, npm view verification steps, and offers a PR; no defect claimed.

    Reproduction reason: The report is a dependency-version bump request and describes no current behavior defect to reproduce; verification would only re-read published registry metadata.


    This summary was generated by an LLM and may contain errors. Please verify its findings.

    Triage bot commands and options

    Repository collaborators with write or admin access can trigger actions by commenting on this issue:

    • @workers-devprod reproduce: Attempt to reproduce the issue using its description and recent comments.
  2. Koslun commented on Nov 14, 2026

    @Koslun
    Author

    Small update to the issue body: I added a TL;DR, linked the CVEs, and clarified that Miniflare’s exposure is unverified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesUsed by dependabot to mark PRs as updates to dependencies.package:miniflareRelating to Miniflare

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    ⌂ 换网址