Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-8769 medium CVSS 4.3

Vulnerability in @ai-sdk/provider-utils (CVE-2026-8769)

Summary

Vulnerability in @ai-sdk/provider-utils (CVE-2026-8769). Risk of unauthorized operations or information disclosure. Exploitable via createJsonResponseHandler. Mitigation: upgrade to 5.0.1 or later.

Original description

The description as published by the source.

Versions of @ai-sdk/provider-utils before 3.0.28, from 4.0.0 before 4.0.33, and from 5.0.0 before 5.0.1 are vulnerable to uncontrolled resource consumption. The createJsonResponseHandler, createJsonErrorResponseHandler, and createStatusCodeErrorResponseHandler functions in packages/provider-utils/src/response-handler.ts read response bodies without a shared size limit, allowing a remote attacker with low privileges to cause excessive memory consumption. The exploit has been publicly disclosed and may be utilized.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-8769 has been found in @ai-sdk/provider-utils.
Attackers can target a specific entry point like createJsonResponseHandler over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade @ai-sdk/provider-utils to 5.0.1 or later.
If unsure, ask your IT team or search "@ai-sdk/provider-utils CVE-2026-8769" on the vendor's site.

CVE-2026-8769 (@ai-sdk/provider-utils) — CWE-400 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: createJsonResponseHandler / createJsonErrorResponseHandler / createStatusCodeErrorResponseHandler
Patched: 5.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in @ai-sdk/provider-utils. Attackers reach the vulnerable code path via createJsonResponseHandler.

📍 Affected scope

Check the vendor advisory for the affected versions of @ai-sdk/provider-utils. Attack surface: createJsonResponseHandler / createJsonErrorResponseHandler / createStatusCodeErrorResponseHandler.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.0.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@ai-sdk/provider-utils' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@ai-sdk/provider-utils' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @ai-sdk/provider-utils を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @ai-sdk/provider-utils to 5.0.1

    ステージング環境で 5.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @ai-sdk/provider-utils
[{"type":"SEMVER","events":[{"introduced":"5.0.0-beta.0"},{"fixed":"5.0.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details