Code Injection in tamagui (CVE-2026-15702)
Summary
Code injection in tamagui (CVE-2026-15702). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-15702 has been found in tamagui.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "tamagui CVE-2026-15702" on the vendor's site.
CVE-2026-15702 (tamagui) — CWE-94 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in tamagui.
Check the vendor advisory for the affected versions of tamagui.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tamagui' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tamagui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tamaguiを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com
- web github.com