tamagui up to 2.3.0 config.ts updateConfig prototype pollution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 2.74 |
Summary
A vulnerability marked as critical has been reported in tamagui up to 2.3.0. This vulnerability affects the function updateConfig of the file code/core/web/src/config.ts. Performing a manipulation results in prototype pollution.
This vulnerability is cataloged as CVE-2026-15702. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in tamagui up to 2.3.0. It has been classified as critical. This affects the function updateConfig of the file code/core/web/src/config.ts. The manipulation with an unknown input leads to a prototype pollution vulnerability. CWE is classifying the issue as CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-15702. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a exploit are known. MITRE ATT&CK project uses the attack technique T1059 for this issue.
It is declared as proof-of-concept.
Upgrading to version 2.3.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch e46af9879b7627934ea4d6d6e46e65cea53abb3d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/tamagui/tamagui/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Prototype pollutionCWE: CWE-1321 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: tamagui 2.3.1
Patch: e46af9879b7627934ea4d6d6e46e65cea53abb3d
Timeline
07/14/2026 Advisory disclosed07/14/2026 VulDB entry created
07/14/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 4029
Status: Confirmed
CVE: CVE-2026-15702 (🔒)
GCVE (CVE): GCVE-0-2026-15702
GCVE (VulDB): GCVE-100-378249
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/14/2026 07:34Changes: 07/14/2026 07:34 (58)
Complete: 🔍
Submitter: wjm1
Cache ID: 216::103
Submit
Accepted
- Submit #856138: Node.js @tamagui/web 2.2.0 Prototype Pollution (by wjm1)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.