CVE Intelligence
Medium Denial of service exploit reference

CVE-2026-8769 — vercel ai provider-utils response-handler.ts createJsonErrorResponseHandler resource consumption

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.

Published May 17, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.7% (30-day exploitation probability)+8
  • Technical severity (medium)+3
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.73%
ahead of 53% of scored CVEs · Oct 14, 2026
Affects
Vercel
Ai and 1 more
CVSS base
6.5
Medium · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Npm @ai-sdk/provider-utils: fixed in version 3.0.28 — github.com (GitHub Security Advisories)
  • Npm @ai-sdk/provider-utils: fixed in version 4.0.33 — github.com (GitHub Security Advisories)
  • Npm @ai-sdk/provider-utils: fixed in version 5.0.1 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Vercel Ai, Npm @ai-sdk/provider-utils).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Vercel Ai ≤ 3.0.97 Vulnerable NIST National Vulnerability Database
Vercel Ai version 3.0.0version 3.0.1version 3.0.2version 3.0.3version 3.0.4version 3.0.5version 3.0.6version 3.0.7
and 90 more version 3.0.8version 3.0.9version 3.0.10version 3.0.11version 3.0.12version 3.0.13version 3.0.14version 3.0.15version 3.0.16version 3.0.17version 3.0.18version 3.0.19version 3.0.20version 3.0.21version 3.0.22version 3.0.23version 3.0.24version 3.0.25version 3.0.26version 3.0.27version 3.0.28version 3.0.29version 3.0.30version 3.0.31version 3.0.32version 3.0.33version 3.0.34version 3.0.35version 3.0.36version 3.0.37version 3.0.38version 3.0.39version 3.0.40version 3.0.41version 3.0.42version 3.0.43version 3.0.44version 3.0.45version 3.0.46version 3.0.47version 3.0.48version 3.0.49version 3.0.50version 3.0.51version 3.0.52version 3.0.53version 3.0.54version 3.0.55version 3.0.56version 3.0.57version 3.0.58version 3.0.59version 3.0.60version 3.0.61version 3.0.62version 3.0.63version 3.0.64version 3.0.65version 3.0.66version 3.0.67version 3.0.68version 3.0.69version 3.0.70version 3.0.71version 3.0.72version 3.0.73version 3.0.74version 3.0.75version 3.0.76version 3.0.77version 3.0.78version 3.0.79version 3.0.80version 3.0.81version 3.0.82version 3.0.83version 3.0.84version 3.0.85version 3.0.86version 3.0.87version 3.0.88version 3.0.89version 3.0.90version 3.0.91version 3.0.92version 3.0.93version 3.0.94version 3.0.95version 3.0.96version 3.0.97
Vulnerable CVE Program (cve.org) e CISA ADP
Npm @ai-sdk/provider-utils < 3.0.28≥ 4.0.0-beta.10 and < 4.0.33≥ 5.0.0-beta.0 and < 5.0.1 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.3 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
2.1 CVSS 4.0 Low — — cna@vuldb.com via NIST National Vulnerability Database
6.5 CVSS 3.1 Medium 2.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
4.3 CVSS 3.1 Medium 2.8 1.4 cna@vuldb.com via NIST National Vulnerability Database
4.3 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
4.3 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
4.3 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
4.0 CVSS 2.0 Medium 8.0 2.9 cna@vuldb.com via NIST National Vulnerability Database
4.0 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 6.5 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-400 · Uncontrolled Resource Consumption

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.73%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Track CPU/memory spikes and availability drops correlated with request patterns.
web/proxy/WAF logsnetwork IDS/IPSresource metrics

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · npm/@ai-sdk/provider-utils
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · vercel/ai
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 17, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

14 on the record

Elsewhere on this site

Vercel
every CVE for this vendor
Denial of service
same class
CWE-400
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-8767 vercel ai PR Branch Name Interpolation prettier-on-automerge.yml run os command injection May 17, 2026
  • CVE-2026-8768 vercel ai provider-utils download-blob.ts validateDownloadUrl server-side request forgery May 17, 2026
  • CVE-2025-48985 Improper Input Validation in Vercel Ai Nov 6, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-8769 is "vercel ai provider-utils response-handler.ts createJsonErrorResponseHandler resource consumption", rated Medium. It affects Ai (Vercel); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.73% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.