Skip to content

chore: upgrade ai to ^6.0.280 to address CVE-2026-8769 - #1639

Open
claude[bot] wants to merge 4 commits into
mainfrom
cursor/cve/ai-sdk-provider-utils
Open

chore: upgrade ai to ^6.0.280 to address CVE-2026-8769#1639
claude[bot] wants to merge 4 commits into
mainfrom
cursor/cve/ai-sdk-provider-utils

Conversation

@claude

@claude claude Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Fixes SOU-2197

Addresses CVE-2026-8769 (Dependabot alert #340) by upgrading the top-level AI SDK dependencies. ai moves to ^6.0.280, @ai-sdk/react to ^3.0.283, and the model providers to compatible patch releases. Every @ai-sdk/provider-utils requester now resolves to patched 4.0.51 through its normal dependency constraints; the resolution override is removed.

Replaces @ai-sdk/mcp@^2.0.0-beta.11 with the maintained, stable AI SDK 6-compatible release ^1.0.80. This is an intentional move back to the 1.x line: it retains the MCP APIs used here, including toolsFromDefinitions, listTools, and OAuth, while sharing provider-utils and tool execution types with ai@6. No context adapter is needed, and the separate provider-utils@5.0.0-beta.7 dependency is also removed.

With the schema types aligned, removes the any cast on MCP input schemas. The existing MCP validation tests now exercise the real AI SDK jsonSchema helper instead of mocking it.

Validation:

  • yarn install --immutable passes (existing peer dependency warnings).
  • yarn why @ai-sdk/provider-utils --recursive shows only 4.0.51, with no override.
  • yarn test: all 2,153 tests pass across four workspaces.
  • yarn workspace @sourcebot/web lint passes.
  • Web tsc --noEmit --incremental false: 67 existing errors; output is byte-for-byte identical to the pre-update PR baseline, with no new errors.

…8769

Every @ai-sdk/* provider package pins @ai-sdk/provider-utils to an exact
version (4.0.23), so neither a lockfile refresh nor a top-level bump that
stays inside the existing ranges can move it. Bumping the top-level
@ai-sdk/* packages to their latest in-range releases does move it, but
also pulls in a breaking `ai` v6 change (ToolExecutionOptions now
requires `context`), which fails typecheck.

Use a qualified resolution keyed to the existing exact source range
instead, which is the narrowest supported fix here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

@claude[bot] your pull request is missing a changelog!

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@claude
claude Bot requested a review from brendan-kellam September 9, 2026 12:52
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

License Audit

❌ Audit failed to produce results. Check the workflow logs for details.

@brendan-kellam brendan-kellam changed the title chore: upgrade @ai-sdk/provider-utils to ^4.0.33 to address CVE-2026-8769 chore: upgrade ai to ^6.0.280 to address CVE-2026-8769 Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant