Quick answers
- Is CVE-2026-8767 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8767 being exploited in the wild.
- How severe is CVE-2026-8767?
- Medium severity, with a CVSS score of 5, published 17 May 2026.
- Which products and versions are affected?
- Vercel AI SDK up to 3.0.97.
- Is there a fix for CVE-2026-8767?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-8767 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8767?
- Check whether you run Vercel AI SDK at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An OS command injection vulnerability exists in the Vercel AI SDK GitHub Actions workflow file `.github/workflows/prettier-on-automerge.yml`. The vulnerability is caused by the direct interpolation of the attacker-controlled branch name (`github.event.pull_request.head.ref`) into a bash script using GitHub Actions' `${{ }}` expression syntax. Although Git branch names have character restrictions, attackers can use subshell execution sequences like `$()` and the Internal Field Separator (`$IFS`) to bypass these limits. An attacker with the ability to submit a pull request can execute arbitrary code in the context of the GitHub Actions runner, potentially accessing secrets like `GH_TOKEN` or deployment keys. The recommended fix is to use intermediate environment variables instead of direct string interpolation.
Affected products
- Vercel AI SDK up to 3.0.97
Timeline
- 2026-04-04: disclosed: Initial discovery and researcher disclosure via Gist
- 2026-05-17: advisory: CVE published to NVD