# CVE-2026-15702: tamagui config.ts updateConfig prototype pollution

> Remote attackers can exploit prototype pollution in Tamagui's updateConfig function to achieve code execution or privilege escalation.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/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:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-p7vf-fh6j-jrm8

## What is CVE-2026-15702?

CVE-2026-15702 is a medium-severity code injection vulnerability in tamagui, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in tamagui up to 2.3.0. This affects the function updateConfig of the file code/core/web/src/config.ts. Such manipulation leads to improperly controlled modification of object prototype attributes. The attack may be performed from remote. Upgrading to version 2.3.1 is able to mitigate this issue. The name of the patch is e46af9879b7627934ea4d6d6e46e65cea53abb3d. The affected component should be upgraded.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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


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

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

## Is CVE-2026-15702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15702 is a medium-severity code injection vulnerability in tamagui, published on 14 Jul 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-15702 exists.

Affected product: tamagui. 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-15702/ (Markdown: https://insights.sbomify.com/CVE-2026-15702/index.md)
```

## Sources

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

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