dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-15702

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a prototype pollution vulnerability in tamagui's updateConfig function in code/core/web/src/config.ts. The function improperly allows modification of object prototype attributes, potentially enabling attackers to inject or manipulate JavaScript object properties at runtime.

MitigationUpgrade tamagui from version 2.3.0 or earlier to version 2.3.1 or later to apply the patch (commit e46af9879b7627934ea4d6d6e46e65cea53abb3d).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate tamagui installation
    Check your project's package.json for tamagui in dependencies or devDependencies, or verify presence in node_modules/tamagui
    Affected if tamagui is not listed in dependencies or not present in node_modules
  2. Identify installed tamagui version
    Run 'npm list tamagui' or 'yarn list tamagui' to see the installed version, or read the version field from node_modules/tamagui/package.json
    Affected if the installed version is 2.3.0 or earlier
  3. Verify vulnerable code path exists
    Inspect the file node_modules/tamagui/code/core/web/src/config.ts (or the built equivalent) and look for the updateConfig function
    Affected if the updateConfig function exists in the expected location and contains logic that processes object attributes without filtering prototype-related keys
  4. Check for usage of updateConfig
    Search your codebase for calls to updateConfig from tamagui, particularly in files that handle user-supplied configuration objects
    Affected if your code calls updateConfig with untrusted input that could include __proto__ or constructor properties

You are affected if tamagui version 2.3.0 or earlier is installed and your code uses the updateConfig function with configuration data that could contain prototype-polluting keys.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade tamagui from version 2.3.0 or earlier to version 2.3.1 or later to apply the patch (commit e46af9879b7627934ea4d6d6e46e65cea53abb3d).

Recommended fix High confidence

tamagui version 2.3.1

  1. 1. Identify the tamagui dependency in your project (check package.json)
  2. 2. Run npm list tamagui or yarn list tamagui to confirm current installed version
  3. 3. If version is 2.3.0 or below, upgrade by running: npm install [email protected] or yarn add [email protected]
  4. 4. Verify the upgrade was successful by running npm list tamagui
  5. 5. Test your application to ensure the upgrade does not break functionality
Caveat No breaking changes documented for this patch release; this is a security fix upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15702 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15702 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data