Packages

@ai-sdk/provider-utils

5.0.83 · 20 Nov 2026Apache-2.076.4M / weekRepositoryHomepagenpmAtom feed

Upgrading @ai-sdk/provider-utils From 4.0.0 to 4.0.67

67 releases in betweennotes for 66

Other targets from 4.0.0Clears its advisory4.0.33Latest5.0.83
  1. 4.0.0yours
  2. 18 releases
  3. 4.0.19security
  4. 4.0.20security
  5. 8 releases
  6. 4.0.29security
  7. 6 releases
  8. 4.0.36security
  9. 20 releases
  10. 4.0.57security
  11. 9 releases
  12. 4.0.67target
?
changes to make
1
advisory fixed
7+
new
44+
fixes

Counted from 66 of 67 release notes. Advisories are counted from the advisory database, in full.

Security

Fixes 1 advisory affecting 4.0.0

  • mcp: Prevent SSRF in OAuth metadata discovery

    4.0.57
  • Prevent prototype pollution when synchronously parsing provider JSON inputs and expose secureJsonParse from provider-utils.

    4.0.36
  • Harden download URL SSRF guard against hostname and redirect bypasses

    4.0.29
  • security: Validate redirect targets in download functions to prevent SSRF bypass

    4.0.20
  • Add URL validation to downloadBlob and download to prevent blind SSRF attacks. Private/internal IP addresses, localhost, and non-HTTP protocols are now rejected before fetching.

    4.0.19

Release by release

  1. 4.0.67

    17 Nov 20261 fix
    • Fixed

      Fix validation of non-Zod Standard Schema results: a result that contains issues is now always treated as a failure, even when it also carries a value. Previously a failing schema such as Valibot's through toStandardJsonSchema() could be reported as valid, so rejected input, including tool input, was accepted.

  2. 4.0.66

    10 Nov 20261 fix
    • Fixed

      Require a DNS-pinned fetch for untrusted MCP OAuth discovery and metadata-derived token/registration URLs on server runtimes without a protected default transport. Preserve developer-configured endpoints and allow explicitly supplied fetch implementations that provide equivalent connect-time validation. Browser workers without a DOM follow the same explicit custom-fetch requirement.

  3. 4.0.65

    7 Nov 20261 fix
    • Fixed

      Reject HTTPS-to-HTTP redirects in validated downloads before requesting the insecure target, including when it matches a configured trusted origin.

  4. 4.0.64

    3 Nov 20261 new · 2 fixes
    • New

      Add stringifyWithBigIntAndCycles for provider tool serialization that converts BigInt values to decimal strings and replaces ancestor cycles while preserving shared references and toJSON behavior.

    • Fixed

      provider-utils: Support cross-realm Uint8Array and ArrayBuffer in binary type guards and base64 conversion

    • Fixed

      provider-utils: Decode base64 into a preallocated Uint8Array to avoid ~25x transient memory and long event-loop blocking on large files

  5. 4.0.63

    29 Oct 20261 fix
    • Fixed

      Use native Buffer base64 encoding when available. encoding a Uint8Array backed by a detached ArrayBuffer now throws a TypeError in runtimes with Buffer instead of returning an empty string

  6. 4.0.62

    21 Oct 20262 fixes
    • Fixed

      Block .internal hostnames in download URL validation.

    • Fixed

      Encode provider-returned identifiers in follow-up request paths with a shared encodePathSegment helper.

  7. 4.0.61

    16 Oct 20261 new
    • New

      openai-compatible: Support URL-based image responses

  8. 4.0.60nothing new or fixed in the note

26 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.