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.
CVE-2026-15702
MEDIUMPre-NVD 6.36.3—Trending — 5 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-14. a secondary CVSS source baseline 6.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EPSS
- 25.9%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026Patch available. Sources: github_release, github_commit.
github_release Patch Available
v2.3.1
Patch available: tamagui/tamagui v2.3.1
https://github.com/tamagui/tamagui/releases/tag/v2.3.1generic
Prototype pollution via public `updateConfig()` API in `@tamagui/web` · Issue #4029 · tamagui/tamagui · GitHub
https://github.com/tamagui/tamagui/issues/4029github_commit Patch Available
commit e46af9879b76 (tamagui/tamagui)
Patch available: tamagui/tamagui v2.3.1 (contains commit e46af9879b76)
https://github.com/tamagui/tamagui/commit/e46af9879b7627934ea4d6d6e46e65cea53abb3dgeneric
GitHub - tamagui/tamagui: Style React fast with 100% parity on React Native, an optional UI kit, and optimizing compiler. · GitHub
https://github.com/tamagui/tamagui/Vendor Advisories for CVE-2026-15702(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:00 UTCEG score recompute
- 2026-07-15 16:00 UTCGHSA enrichment
- 2026-07-15 14:22 UTCNVD updateCVSS v4 → 2.1
- 2026-07-15 13:29 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-07-14 17:20 UTCNVD updateCVSS v4 → 2.1
- 2026-07-14 17:10 UTCEG score recompute
- 2026-07-14 17:10 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(5)
What is CVE-2026-15702?
CVE-2026-15702 is a medium vulnerability published on July 14, 2026. 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…
When was CVE-2026-15702 disclosed?
CVE-2026-15702 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15702 actively exploited?
CVE-2026-15702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15702?
CVE-2026-15702 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-15702?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15702, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15702
Is Your Infrastructure Affected by CVE-2026-15702?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.