CVE-2026-15607
Deferred Deferred - Pending Action

Prototype Pollution in TanStack DB

Vulnerability report for CVE-2026-15607, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-13

Last updated on: 2026-07-15

Assigner: VulDB

Description

A vulnerability was detected in tanstack db up to 0.6.8. Affected by this vulnerability is the function select of the file src/query/compiler/select.ts of the component Alias Path Handler. The manipulation results in improperly controlled modification of object prototype attributes. The attack may be launched remotely. The exploit is now public and may be used. The patch is identified as ac09b1177a100eafa85cba3cd09dd1f53f933ded. A patch should be applied to remediate this issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-13
Last Modified
2026-07-15
Generated
2026-08-03
AI Q&A
2026-07-14
EPSS Evaluated
2026-08-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tanstack db to 0.6.8 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
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.
CWE-94 The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-15607 is a vulnerability in tanstack db versions up to 0.6.8. The issue occurs in the function 'select' located in the file 'src/query/compiler/select.ts' within the component called Alias Path Handler.

The vulnerability involves improperly controlled modification of object prototype attributes. This means an attacker could manipulate JavaScript object prototypes, potentially leading to unintended behavior or security issues in the application.

The attack can be launched remotely, and an exploit for this vulnerability is publicly available. A patch has been released to fix this issue, identified as ac09b1177a100eafa85cba3cd09dd1f53f933ded.

Detection Guidance

Detecting this vulnerability requires checking if your system is running an affected version of tanstack db (up to 0.6.8). Since the vulnerability is related to the function 'select' in the file 'src/query/compiler/select.ts' and involves improperly controlled modification of object prototype attributes, you can follow these steps:

  • Identify if tanstack db is installed in your environment. You can search for its installation directory or check package manifests (e.g., package.json for Node.js projects).
  • Verify the version of tanstack db. If it is version 0.6.8 or earlier, the system is vulnerable. For Node.js projects, you can run: npm list @tanstack/db or check the package.json file directly.
  • Inspect the codebase for the presence of the vulnerable file path: 'src/query/compiler/select.ts'. If this file exists and the version is vulnerable, the system may be at risk.
  • Monitor network traffic for unusual patterns that might indicate exploitation attempts, such as unexpected modifications to object prototypes in API requests or responses.

There are no specific commands provided in the context for automated detection, but manual inspection of the installed version and codebase is recommended.

Impact Analysis

This vulnerability could impact you in several ways if you are using an affected version of tanstack db (up to 0.6.8):

  • An attacker could remotely exploit this vulnerability to manipulate object prototypes in your application. This may lead to unexpected behavior, such as data corruption or unauthorized data access.
  • Since the exploit is public, the risk of exploitation is higher, as attackers may already have tools or scripts to take advantage of this flaw.
  • The CVSS v3.1 score of 4.3 (Medium severity) indicates that the vulnerability could allow low-privileged users to modify data integrity (I:L), though it does not directly impact confidentiality or availability.

If your application relies on tanstack db for data handling, this vulnerability could undermine the security and reliability of your system.

Compliance Impact

The impact of this vulnerability on compliance with standards and regulations depends on how tanstack db is used in your environment:

  • GDPR: If the vulnerability leads to unauthorized data modification or access, it could result in a breach of data integrity or confidentiality. Under GDPR, this may require notification to authorities and affected individuals if personal data is compromised.
  • HIPAA: If tanstack db is used to handle protected health information (PHI), this vulnerability could violate HIPAA's security rule, which requires safeguards to ensure the integrity and confidentiality of PHI. A successful exploit could lead to non-compliance and potential penalties.
  • Other standards: Many compliance frameworks (e.g., ISO 27001, SOC 2) require organizations to maintain secure systems and protect against known vulnerabilities. Failure to patch this vulnerability could result in non-compliance with such standards.

Since the vulnerability involves improperly controlled modification of object prototype attributes, it could indirectly affect data integrity, which is a key concern for most compliance regulations.

Mitigation Strategies

To mitigate this vulnerability, follow these immediate steps:

  • Apply the available patch identified as ac09b1177a100eafa85cba3cd09dd1f53f933ded. This patch addresses the improperly controlled modification of object prototype attributes in the 'select' function.
  • Upgrade tanstack db to a version beyond 0.6.8, if available. Since the context does not specify a fixed version, ensure you are using the latest release that includes the patch.
  • If upgrading or patching is not immediately possible, consider implementing temporary workarounds such as input validation or sanitization to prevent manipulation of object prototype attributes.
  • Restrict access to the affected component by limiting user privileges (e.g., ensuring only trusted users with 'PR:L' or higher privileges can interact with the system).
  • Monitor systems for signs of exploitation, such as unexpected behavior in object prototypes or unusual API requests.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-15607. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart