CVE-2026-106160 is a prototype pollution vulnerability in Progress Software Kendo UI for jQuery versions from 2023.1.117 up to but not including 2026.3.1015. The issue arises because the Model.accept function passes server-response keys to kendo.setter without properly filtering unsafe object paths such as __proto__, constructor, or prototype. This allows an attacker who can supply crafted data to modify object prototype attributes, potentially affecting application behavior and compromising confidentiality and integrity of data. The vulnerability is fixed in version 2026.3.1015.
Perforce Helix Authentication Service (HAS) versions 2022.1 through 2025.2 contain a vulnerability due to the retention of a default SCIM bearer token in the installation templates. This default token is copied into the active configuration without automatic replacement, allowing an attacker who knows the token to authenticate to the SCIM API and perform user and group operations. The vulnerability was fixed in version 2026.1, released on July 17, 2026.
A prototype pollution vulnerability exists in msgpack5 versions prior to 6.1.0. When constructed with an empty or partial options object, the default protection against prototype pollution is disabled. This allows a decoded map containing a __proto__ key to replace the decoded object's prototype, potentially altering inherited properties or downstream behavior. The global Object.prototype is not affected. The issue is fixed in version 6.1.0.
traverse (npm) versions 0.3.6 through 0.3.9, 0.4.0 through 0.4.6, 0.5.0 through 0.5.2, and 0.6.0 through 0.6.11 allow prototype pollution through set(). When the path passed to set() crosses a primitive value, the next path segment is resolved on that primitive's built-in prototype, so an application that passes an untrusted path to set() lets an attacker add or overwrite properties of String.prototype, Number.prototype, or Boolean.prototype using plain JSON data, for example traverse({ name: 'bob' }).set(['name', '__proto__', 'polluted'], 'yes'). Object.prototype was reachable only with a non-data path segment, such as an object whose toString returns a different value on each call, or through a Proxy that accepts an assignment without storing it. This is fixed in 0.3.10, 0.4.7, 0.5.3, and 0.6.12.
Mozilla's Node-convict version 6.2.2 is affected by a prototype pollution vulnerability in the config.set() function. This flaw allows an attacker who can control configuration keys to overwrite core JavaScript methods such as Object.assign by writing arbitrary properties to constructor.<key>. The vulnerability bypasses existing filters and can cause persistent process-wide failures, resulting in denial of service that requires a restart. Exploitation requires an endpoint that forwards attacker-controlled keys into config.set().
PayloadCMS versions prior to 3.90.0 and canary versions before 4.0.0-canary.34 contain a code injection vulnerability in the public first-register operation. This flaw allows remote code execution when local authentication is enabled and no initial user has been created. The vulnerability is addressed in versions 3.90.0 and 4.0.0-canary.34.
## Impact
A vulnerability in `@payloadcms/plugin-form-builder` in versions < 3.90.0 allow submissions which could be crafted to execute remote code on the server.
**You are affected if:**
- You are using `@payloadcms/plugin-form-builder`
## Patches
Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.
PayloadCMS versions from 3.0.0 up to but not including 3.88.0, and canary versions from 4.0.0-canary.0 up to but not including 4.0.0-canary.27, contain a prototype pollution vulnerability in the @payloadcms/plugin-import-export plugin. This vulnerability allows unauthenticated users to submit prototype-sensitive field paths, leading to unintended application behavior and potential remote code execution. The issue is fixed in versions 3.88.0 and 4.0.0-canary.27.
GraphQL Tools provides utilities for building, stitching, and mocking GraphQL schemas. Prior to 12.0.1, the GraphQL Tools utils package's mergeDeep function follows inherited properties while recursively merging source objects and does not exclude __proto__, constructor, or prototype keys. An unauthenticated GraphQL client can alias fields to those names so responses from two subgraphs collide during ordinary supergraph result merging, causing mergeDeep to traverse Object and Function prototypes and overwrite Function.prototype.call with a subgraph-supplied value. This breaks subsequent requests in the process until restart. This issue is fixed in version 12.0.1.
CVE-2026-103918 is a medium severity vulnerability in the middleapi orpc package affecting the ZodSmartCoercionPlugin and experimental_ZodSmartCoercionPlugin. These plugins improperly handle object keys that match Object.prototype members, allowing an attacker to replace the prototype of a coerced input object or cause unhandled TypeErrors by sending keys like 'constructor'. The issue is limited to the request payload and does not affect global state or other requests. It is fixed in version 1.14.10.
CVE-2026-103036 is a medium severity vulnerability in the orpc component of middleapi prior to version 1.14.9. It involves improper control of dynamically-determined object attributes during JSON schema coercion, allowing a remote client to supply crafted __proto__ or Object.prototype properties that influence the behavior of the coerced request object. This can affect handler logic and configuration lookups without modifying global objects or other users' requests. The issue is fixed in version 1.14.9.
Tinypool versions prior to 2.1.2 contain a code injection vulnerability due to improper handling of the filename property in the options object passed to pool.run(). An attacker who can pollute Object.prototype.filename can cause the worker pool to load malicious JavaScript code, potentially leading to arbitrary code execution with the host process's privileges. This vulnerability is fixed in version 2.1.2.
Tinypool is a minimal Node.js worker thread pool implementation. Prior to 2.1.1, Tinypool constructs ThreadPool.options from a normal options object and reads the execArgv and env worker options in dist/index.js, allowing values inherited from a polluted Object.prototype to be copied into own properties and passed to worker_threads.Worker. An attacker who can first pollute either property can cause each newly spawned worker to load attacker-selected JavaScript through command-line preload arguments or NODE_OPTIONS, resulting in code execution with the host process's privileges and possible access to CI secrets, signing material, or build artifacts. This issue is fixed in version 2.1.1.
CVE-2026-94646 is a high-severity vulnerability in Apache Thrift's Node.js bindings affecting versions before 0.25.0. It involves uncaught exceptions, improper validation of input quantities, and prototype pollution due to improperly controlled modification of object prototype attributes. This vulnerability can lead to significant security risks if exploited. Users are advised to upgrade to version 0.25.0, which addresses and fixes the issue.
CVE-2026-86535 is a high-severity vulnerability in Apache Thrift NodeJS bindings involving an infinite loop caused by a loop with an unreachable exit condition and prototype pollution. This affects versions before 0.25.0. The issue is fixed in version 0.25.0, and users are advised to upgrade.
Improperly controlled modification of object prototype attributes ('prototype pollution') vulnerability in Apache Thrift all JS bindings.
This issue affects Apache Thrift: before 0.25.0.
Users are recommended to upgrade to version 0.25.0 and re-generate JS code, which fixes the issue.
CVE-2026-104183 is a prototype pollution vulnerability in the uhop stream-json library prior to version 3.6.0. The vulnerability arises because the Assembler component assigns object properties using plain assignment, allowing an input key named __proto__ to modify the prototype of parsed objects. This can lead to attacker-controlled inherited properties affecting application logic that relies on prototype values. The global Object.prototype is not affected. The issue is fixed in version 3.6.0.
CVE-2026-102992 is a critical prototype pollution vulnerability in the Node.js worker pool implementation piscina. Versions prior to 4.9.4, 5.3.2, and 6.0.0-rc.5 are affected. The issue arises because ThreadPool.options is stored as a plain object inheriting from Object.prototype, allowing attackers to supply inherited values for security-sensitive options. This can lead to attacker-controlled code execution in worker threads via inherited execArgv, loadBalancer, or env values. The vulnerability is fixed in versions 4.9.4, 5.3.2, and 6.0.0-rc.5.
Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 0.1.1, @socket.io/cluster-engine uses inherited object properties when looking up attacker-controlled session IDs in clustered deployments. Special property names such as __proto__ or constructor can resolve through the object prototype chain instead of identifying an actual connected client, causing the Node.js process to crash and resulting in denial of service. Applications that do not use @socket.io/cluster-engine are not affected. This issue is fixed in version 0.1.1.
A prototype pollution vulnerability in Software Mansion React Native Worklets before 0.12.2 allows an attacker-controlled object containing a __proto__ property to modify the prototype of an object created during serialization in clonePlainJSObject in packages/react-native-worklets/src/memory/serializable.native.ts. When affected data is subsequently processed by React Native Worklets, the malformed serialized object can cause the React Native application to crash. This can result in a remotely triggered denial of service in applications that pass attacker-controlled data through the affected serialization path. In applications where the attacker-controlled data is persisted, the denial of service may persist across application restarts or repeated attempts to access the affected content.