# CVE-2026-8767: vercel ai PR Branch Name Interpolation prettier-on-automerge.yml run os command injection

> Remote attackers can execute arbitrary OS commands via PR branch name interpolation in the Vercel AI SDK CI workflow.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-9pj2-3x6v-c3pp

## What is CVE-2026-8767?

CVE-2026-8767 is a low-severity command injection vulnerability in vercel ai, published on 17 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in vercel ai up to 3.0.97. Impacted is the function run of the file .github/workflows/prettier-on-automerge.yml of the component PR Branch Name Interpolation. The manipulation leads to os command injection. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitability is considered difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-8767?

It affects 1 product.


Products: Vercel Ai.

## How do I fix CVE-2026-8767?

No fix has been published for CVE-2026-8767 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8767 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8767 exists.

## Other vulnerabilities in vercel ai

- [CVE-2026-8768](https://insights.sbomify.com/CVE-2026-8768/): vercel ai provider-utils download-blob.ts validateDownloadUrl server-side request forgery (medium 6.9)
- [CVE-2026-8769](https://insights.sbomify.com/CVE-2026-8769/): vercel ai provider-utils response-handler.ts createJsonErrorResponseHandler resource consumption (medium 5.3)
- [CVE-2025-48985](https://insights.sbomify.com/CVE-2025-48985/): Vercel’s AI SDK's filetype whitelists can be bypassed when uploading files (low 3.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8767 and fix it if it is affected.

What it is: CVE-2026-8767 is a low-severity command injection vulnerability in vercel ai, published on 17 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8767 exists.

Affected product: vercel ai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8767/ (Markdown: https://insights.sbomify.com/CVE-2026-8767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8767
- OSV: https://osv.dev/vulnerability/CVE-2026-8767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8767/
Summaries are generated and may contain mistakes; the official description above is the record.