Skip to main content

Vercel AI SDK CVE-2026-8769

| EUVDEUVD-2026-30712 LOW
Uncontrolled Resource Consumption (CWE-400)
2026-05-17 cna@vuldb.com GHSA-866g-f22w-33x8
2.1
CVSS 4.0 · Vendor: vuldb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to target application
  2. Exploit
    Send crafted JSON to AI endpoint
  3. Execution
    Trigger excessive resource allocation in response handler
  4. Impact
    Degrade service availability

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK

1 technique across 1 tactic: Impact

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires authenticated access (PR:L) to an application using Vercel AI SDK versions ≤3.0.97. Specifically exploitable when the application invokes createJsonResponseHandler or createJsonErrorResponseHandler functions in the provider-utils package to process AI provider responses. Attack surface is limited to network-accessible endpoints that accept user-controlled data passed to these JSON response handlers. Exploitation is bounded by authentication requirements - not exploitable by anonymous attackers against default configurations. Rate limiting, WAF rules, or SDK-level resource quotas would further limit exploitation feasibility.

Impact

Real-world risk is LOW despite the availability of public exploit code. CVSS 4.0 vector analysis reveals: network-accessible (AV:N) with low complexity (AC:L) but requires authentication (PR:L), limiting the attack surface to authorized users or compromised accounts. Impact is confined to low availability degradation (VA:L) with no confidentiality or integrity effects (VC:N/VI:N). Exploit maturity indicator (E:P) confirms proof-of-concept exists, but absence from CISA KEV and the 2.1 severity score indicate no evidence of real-world exploitation campaigns. The requirement for authentication significantly reduces exploitation probability compared to unauthenticated resource consumption flaws. SSVC prioritization would likely categorize this as 'scheduled' rather than urgent - the technical impact is limited to service degradation, not system compromise, and exploitation is not automatable at scale without credential access. Primary concern is for high-volume AI applications where authenticated users could intentionally degrade service quality, but defense-in-depth measures like rate limiting and resource quotas typically mitigate such attacks independently of patching.

Exploit ScenarioDerived

An authenticated user with valid credentials to an application using Vercel AI SDK sends a specially crafted request containing malicious JSON structures designed to trigger excessive resource consumption in the createJsonResponseHandler function. The handler attempts to process the adversarial JSON payload without adequate resource constraints, causing the application to allocate excessive memory or CPU cycles. This degrades service availability for other users, potentially causing timeouts or service slowdowns. With public POC code available and low attack complexity (AC:L), exploitation is straightforward for any authenticated user.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 17, 2026

Resource exhaustion in Vercel AI SDK's provider-utils package (versions ≤3.0.97) allows authenticated remote attackers to consume excessive system resources via specially crafted requests to JSON response handlers. Public proof-of-concept exists. EPSS data not available. Not listed in CISA KEV. CVSS 4.0 score of 2.1 reflects low availability impact (VA:L) with authenticated network access (PR:L). Vendor non-responsive to initial disclosure.

RemediationAI

No vendor-released patch identified at time of analysis - Vercel did not respond to initial vulnerability disclosure per VulDB submission 811406. Organizations using Vercel AI SDK ≤3.0.97 should implement compensating controls: Apply rate limiting at the application layer to restrict request frequency per authenticated user (limit: 10-50 requests/minute depending on use case; trade-off: may impact legitimate high-volume users). Configure resource quotas for SDK operations using container memory limits or Node.js --max-old-space-size flag (trade-off: may cause crashes under legitimate load spikes rather than graceful degradation). Deploy request timeout enforcement (recommended: 30-60 seconds for AI operations; trade-off: may prematurely terminate valid long-running AI requests). Monitor resource consumption metrics for anomalies using application performance monitoring tools. Check Vercel AI SDK GitHub repository (vercel/ai) for community patches or newer releases beyond 3.0.97 that may address the issue. Public POC available at https://gist.github.com/YLChen-007/fb1096bc8428bed9a428f764d9d103bb for testing effectiveness of mitigations.

Affected VersionsENISA

AI 3.0.83
AI 3.0.58
AI 3.0.7
AI 3.0.41
AI 3.0.31
AI 3.0.14
AI 3.0.22
AI 3.0.21
AI 3.0.27
AI 3.0.59
AI 3.0.64
AI 3.0.22
AI 3.0.8
AI 3.0.55
AI 3.0.93
AI 3.0.10
AI 3.0.33
AI 3.0.43
AI 3.0.68
AI 3.0.26
AI 3.0.89
AI 3.0.16
AI 3.0.57
AI 3.0.37
AI 3.0.10
AI 3.0.62
AI 3.0.49
AI 3.0.40
AI 3.0.32
AI 3.0.53
AI 3.0.49
AI 3.0.33
AI 3.0.17
AI 3.0.29
AI 3.0.52
AI 3.0.83
AI 3.0.30
AI 3.0.91
AI 3.0.69
AI 3.0.23
AI 3.0.61
AI 3.0.81
AI 3.0.71
AI 3.0.36
AI 3.0.86
AI 3.0.35
AI 3.0.6
AI 3.0.53
AI 3.0.36
AI 3.0.85
AI 3.0.76
AI 3.0.48
AI 3.0.65
AI 3.0.94
AI 3.0.18
AI 3.0.74
AI 3.0.92
AI 3.0.81
AI 3.0.58
AI 3.0.2
AI 3.0.47
AI 3.0.0
AI 3.0.40
AI 3.0.54
AI 3.0.31
AI 3.0.57
AI 3.0.48
AI 3.0.15
AI 3.0.21
AI 3.0.28
AI 3.0.7
AI 3.0.50
AI 3.0.73
AI 3.0.44
AI 3.0.73
AI 3.0.65
AI 3.0.1
AI 3.0.30
AI 3.0.71
AI 3.0.97
AI 3.0.62
AI 3.0.91
AI 3.0.66
AI 3.0.61
AI 3.0.28
AI 3.0.72
AI 3.0.63
AI 3.0.70
AI 3.0.45
AI 3.0.66
AI 3.0.3
AI 3.0.43
AI 3.0.39
AI 3.0.29
AI 3.0.69
AI 3.0.95
AI 3.0.38
AI 3.0.39
AI 3.0.92
AI 3.0.16
AI 3.0.59
AI 3.0.67
AI 3.0.82
AI 3.0.27
AI 3.0.90
AI 3.0.50
AI 3.0.51
AI 3.0.88
AI 3.0.56
AI 3.0.89
AI 3.0.54
AI 3.0.84
AI 3.0.68
AI 3.0.94
AI 3.0.24
AI 3.0.85
AI 3.0.15
AI 3.0.96
AI 3.0.35
AI 3.0.70
AI 3.0.45
AI 3.0.25
AI 3.0.79
AI 3.0.26
AI 3.0.67
AI 3.0.4
AI 3.0.75
AI 3.0.95
AI 3.0.93
AI 3.0.75
AI 3.0.90
AI 3.0.97
AI 3.0.0
AI 3.0.6
AI 3.0.20
AI 3.0.8
AI 3.0.34
AI 3.0.17
AI 3.0.47
AI 3.0.5
AI 3.0.24
AI 3.0.3
AI 3.0.9
AI 3.0.64
AI 3.0.74
AI 3.0.19
AI 3.0.80
AI 3.0.44
AI 3.0.84
AI 3.0.52
AI 3.0.42
AI 3.0.38
AI 3.0.96
AI 3.0.60
AI 3.0.77
AI 3.0.9
AI 3.0.12
AI 3.0.87
AI 3.0.5
AI 3.0.78
AI 3.0.2
AI 3.0.4
AI 3.0.46
AI 3.0.76
AI 3.0.63
AI 3.0.34
AI 3.0.1
AI 3.0.86
AI 3.0.25
AI 3.0.77
AI 3.0.41
AI 3.0.11
AI 3.0.88
AI 3.0.11
AI 3.0.23
AI 3.0.72
AI 3.0.79
AI 3.0.55
AI 3.0.19
AI 3.0.51
AI 3.0.37
AI 3.0.20
AI 3.0.56
AI 3.0.82
AI 3.0.87
AI 3.0.14
AI 3.0.78
AI 3.0.13
AI 3.0.12
AI 3.0.60
AI 3.0.32
AI 3.0.42
AI 3.0.13
AI 3.0.18
AI 3.0.80
AI 3.0.46

Affected Packages

npm @ai-sdk/provider-utils fix: 3.0.28, 4.0.33, 5.0.1
euvd ai no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in npm, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the provider-utils package of the Vercel AI SDK, specifically in the createJsonResponseHandler and createJsonErrorResponseHandler functions within response-handler.ts. Classified as CWE-400 (Uncontrolled Resource Consumption), this indicates insufficient limits on resource allocation when processing JSON responses. The Vercel AI SDK provides abstractions for working with AI model providers, and the affected response handlers are likely involved in parsing and processing JSON payloads from AI service responses. Without proper input validation or resource constraints, specially crafted JSON structures could trigger excessive memory allocation, CPU consumption, or processing time, leading to denial of service conditions for the application using the SDK.

Know when Ai gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (vuldb) PRIMARY 2.1 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

Primary rating from Vendor (vuldb) · only source for this CVE.

CVSS VectorVendor: vuldb

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A vulnerability was determined in vercel ai up to 3.0.97. The impacted element is the function createJsonResponseHandler/createJsonErrorResponseHandler of the file packages/provider-utils/src/response-handler.ts of the component provider-utils. This manipulation causes resource consumption. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

10
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy