[dependabot]

Bumps undici to 7.30.1 and updates ancestor dependency cf. These dependencies need to be updated together.

Updates undici from 7.29.1 to 7.30.1

Release notes

Sourced from undici's releases.

v7.30.1

Security fixes

High severity

Denial of service via TLS 1.2 certificate-changing renegotiation

CVE-2026-87018 · GHSA-qrxm-fqhp-jwvm

A malicious or compromised HTTPS server could crash the Node.js process by initiating TLS 1.2 renegotiation and presenting a different, CA-trusted certificate whose hostname did not match the requested host. The resulting socket error reached an assertion in undici's HTTP/1.1 and HTTP/2 connection handling. This release handles post-connect certificate errors without terminating the process.

TLS certificate validation bypass through dropped Agent options

CVE-2026-109383 · GHSA-2m5v-pch6-74hx

Agent used a JSON-based clone for constructor options, which silently removed function-valued TLS options such as checkServerIdentity. Applications relying on custom certificate or public-key verification could therefore accept a certificate that the callback was intended to reject. This release preserves TLS options when creating per-origin dispatchers.

Cache poisoning and cross-user disclosure through cross-origin redirects

CVE-2026-109829 · GHSA-4w7w-5xrc-9h26

When an originless Agent combined redirect and shared-cache interceptors as compose(redirect(), cache()), a response from a cross-origin redirect could be stored under the original URL. This could allow persistent cache poisoning or disclosure of user-specific responses to later callers. This release verifies the response origin before caching and preserves redirect-hop cache-control policy.

Denial of service through excessive Content-Encoding values

CVE-2026-109869 · GHSA-xjj6-f33q-929c

A malicious HTTP server could crash the Node.js process by returning more than five content codings and closing the connection before sending the body. Although fetch() rejected the response, an error from an orphaned internal stream could remain unhandled. This release validates the content-encoding chain before creating the body stream and aborts oversized chains safely.

Medium severity

Denial of service through the decompress interceptor

CVE-2026-87029 · GHSA-55wc-3pg8-jfw6

An exception thrown by a downstream response handler from an asynchronous decompression callback could escape as an uncaught exception. A server could trigger this when decompress was composed with a handler such as dump with a size limit. This release converts downstream handler exceptions into per-request errors.

Subresource Integrity bypass with non-lowercase algorithm tokens

CVE-2026-109841 · GHSA-f72v-6w45-q472

fetch() treated valid mixed-case or uppercase SRI algorithm tokens, such as SHA256, as unknown and could accept a response whose body did not match the configured digest. This release normalizes algorithm tokens before validation and digest selection.

Denial of service through unbounded EventSource parser state

CVE-2026-109924 · GHSA-4qv8-2p9j-2685

A malicious Server-Sent Events endpoint could exhaust process memory by sending many tiny data: fields without completing an event, or by splitting an unfinished line across many chunks. This release bounds retained EventSource parser state, including field counts, buffered chunks, unfinished-line length, and retained field data.

Denial of service through unbounded automatic WebSocket PONG buffering

... (truncated)

Commits

• 7507102 Bumped v7.30.1 (#6022)
• 7d60c7b [v7.x] fix(cookies): backport #5663, #5808 and #5832 (#6019)
• 0227d5d fix: avoid unbounded recursion in Set-Cookie attribute parser (#5757) (#5997)
• 5394462 fix(websocket): bound automatic PONG writes under backpressure
• 2991627 fix(eventsource): bound retained SSE parser state
• 18bc8a1 fix(sri): accept non-lowercase algorithm tokens
• 63cba77 fix(decompress): converge downstream handler throws to per-request errors
• 07ded49 fix(fetch): abort excessive content encoding responses
• b20b82a fix(cache): prevent cross-origin redirect cache confusion
• 04cb74b fix: preserve Agent connection options
• Additional commits viewable in compare view

Updates cf from 1.0.0-beta.18 to 1.0.0-beta.28

Release notes

Sourced from cf's releases.

cf@1.0.0-beta.28

Minor Changes

• ab9613a: Update the generated command surface for Forge OpenAPI release 57b5196b0cb64ae395bebc71f9a933eeda99bf64.

• 7ef1a2e: Validate array body limits instead of batching requests

  Reject JSON array bodies that exceed the API schema's maxItems, including inline input, files, and dry runs. Remove automatic request batching for every HTTP method so array limits cannot silently change an operation's meaning or lose results.

Patch Changes

• 775a37f: Include destructive confirmation flags in command metadata

  Expose --force and its -f alias in shell completions and other metadata consumers for generated DELETE commands and operations that require confirmation.

• b5c5756: Correct action labels for commands that require confirmation

  Show Updating/Updated for confirmed PUT and PATCH operations and neutral Processing/Done labels for confirmed POST actions. Keep their operation-specific warnings and --force behavior, and reject missing required --body input before asking for confirmation.

• a0eed39: Upload binary multipart arrays as file parts

  Fix cf ai to-markdown --file path to upload under the API's files field. Accept multiple files with --files @first.html @second.pdf or repeated --files flags, preserving each file's bytes and filename.

• 7619cbd: Normalize generated option names in command metadata

  Use the command builder's kebab-case normalization for option metadata so completions and tools advertise the flags accepted by existing commands.

• 707e9ac: Describe plain-text --body correctly in command metadata

  For commands that send --body as text/plain, command metadata used by cf tools now gives the same description as --help instead of asking for raw JSON. This includes media types with parameters such as text/plain;charset=UTF-8. When no description is provided, both metadata and --help use plain-text wording.

• 5b21733: Keep CLI usage errors concise

  Exit with an error for unknown top-level and nested command names followed by --help or -h. Show concise errors and italic hints to the relevant help command. Unknown global flags also list the available global flags.

• f1e1d11: Update dependencies published from the Workers SDK repository:

  • @cloudflare/autoconfig: 0.9.2 → 0.9.3

... (truncated)

Changelog

Sourced from cf's changelog.

1.0.0-beta.28

Minor Changes

• ab9613a: Update the generated command surface for Forge OpenAPI release 57b5196b0cb64ae395bebc71f9a933eeda99bf64.

• 7ef1a2e: Validate array body limits instead of batching requests

  Reject JSON array bodies that exceed the API schema's maxItems, including inline input, files, and dry runs. Remove automatic request batching for every HTTP method so array limits cannot silently change an operation's meaning or lose results.

Patch Changes

• 775a37f: Include destructive confirmation flags in command metadata

  Expose --force and its -f alias in shell completions and other metadata consumers for generated DELETE commands and operations that require confirmation.

• b5c5756: Correct action labels for commands that require confirmation

  Show Updating/Updated for confirmed PUT and PATCH operations and neutral Processing/Done labels for confirmed POST actions. Keep their operation-specific warnings and --force behavior, and reject missing required --body input before asking for confirmation.

• a0eed39: Upload binary multipart arrays as file parts

  Fix cf ai to-markdown --file path to upload under the API's files field. Accept multiple files with --files @first.html @second.pdf or repeated --files flags, preserving each file's bytes and filename.

• 7619cbd: Normalize generated option names in command metadata

  Use the command builder's kebab-case normalization for option metadata so completions and tools advertise the flags accepted by existing commands.

• 707e9ac: Describe plain-text --body correctly in command metadata

  For commands that send --body as text/plain, command metadata used by cf tools now gives the same description as --help instead of asking for raw JSON. This includes media types with parameters such as text/plain;charset=UTF-8. When no description is provided, both metadata and --help use plain-text wording.

• 5b21733: Keep CLI usage errors concise

  Exit with an error for unknown top-level and nested command names followed by --help or -h. Show concise errors and italic hints to the relevant help command. Unknown global flags also list the available global flags.

• f1e1d11: Update dependencies published from the Workers SDK repository:

... (truncated)

Commits

• b5ce1c4 Version Packages (beta) (#486)
• ab9613a chore: update OpenAPI to 57b5196b0cb6 (#477)
• f1e1d11 fix(deps): update workers-sdk derived dependencies (#517)
• 9a061fa fix: resolve allOf field types in OpenAPI compatibility guard (#512)
• 1de7b1b fix: validate --body before confirmation prompts (#504)
• 707e9ac fix: describe plain-text --body correctly in command metadata (#506)
• 33f2847 chore(deps): update @​cloudflare/forge digest to 0118fdf (#508)
• 5b21733 fix: reject unknown help commands and shorten usage errors (#146)
• 16cd290 fix: verify scoped API token status in auth whoami (#119)
• a0eed39 fix: upload binary multipart arrays as files (#501)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[dependabot]

Looks like these dependencies are no longer a dependency, so this is no longer needed.