50 matches found
CVE-2026-116321 PostgreSQL unterminated name value discloses server memory
Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via changing the final byte of a fixed-length name value to a nonzero byte and passing it to code that treats the value as a C string. Versions before PostgreSQL 18.7, 17.12, 16.16,...
PT-2026-145812
Name of the Vulnerable Software and Affected Versions PostgreSQL versions prior to 18.7 PostgreSQL versions prior to 17.12 PostgreSQL versions prior to 16.16 PostgreSQL versions prior to 15.20 PostgreSQL versions prior to 14.25 Description Improper null termination during array element assignment...
Vulnerability in core server (CVE-2026-116321)
PostgreSQL unterminated name value discloses server memory Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via changing the final byte of a fixed-length name value to a nonzero byte and passing it to code that treats the value as ...
CVE-2026-116321: n/a PostgreSQL: Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via…
Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via changing the final byte of a fixed-length name value to a nonzero byte and passing it to code that treats the value as a C string. Versions before PostgreSQL 18.7, 17.12, 16.16,...
CVE-2026-111768 Model Context Protocol TypeScript SDK: One HTTP request within the default size limit could exhaust server memory during validation
The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 1.3.0 until 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/server, HTTP servers did not enforce a limit on the number of arr...
CVE-2026-111768
The Model Context Protocol TypeScript SDK is vulnerable to a memory exhaustion issue where a single HTTP request within the default 4 MiB limit can terminate the process due to JavaScript heap exhaustion . The root cause is the lack of enforced limits on the number of array elements and object ke...
CVE-2026-110879 jackson-databind: PolymorphicTypeValidator bypass via generic type arguments and array element types allows arbitrary class instantiation (incomplete fix for CVE-2026-54512)
jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes inside its generic arguments, even when those classes violate the declared type or would be rejected as direct type IDs. This bypasses the generic-argument validation added for CVE-2026-54512...
CVE-2026-110879 jackson-databind: PolymorphicTypeValidator bypass via generic type arguments and array element types allows arbitrary class instantiation (incomplete fix for CVE-2026-54512)
jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes inside its generic arguments, even when those classes violate the declared type or would be rejected as direct type IDs. This bypasses the generic-argument validation added for CVE-2026-54512...
CVE-2026-110879 jackson-databind: PolymorphicTypeValidator bypass via generic type arguments and array element types allows arbitrary class instantiation (incomplete fix for CVE-2026-54512)
jackson-databind validates the outer class of a class-name type ID but accepts attacker-selected classes inside its generic arguments, even when those classes violate the declared type or would be rejected as direct type IDs. This bypasses the generic-argument validation added for CVE-2026-54512...
CVE-2026-110879
The jackson-databind library (com.fasterxml.jackson.core:jackson-databind from version 2.10.0 and tools.jackson.core:jackson-databind from version 3.0.0 ) contains a PolymorphicTypeValidator bypass. The vulnerability occurs because the library validates the outer class of a class-name type ID but...
CLSA-2026-1787889621 jackson-databind: Fix of CVE-2026-54513
CVE-2026-54513: fix BasicPolymorphicTypeValidator allowIfSubTypeIsArray to validate array element type...
GHSA-8RW6-P7M8-63JP SurrealDB: Array element-level (field.*) SELECT permissions leak denied elements to record users
A SELECT permission defined on an array element DEFINE FIELD field. … PERMISSIONS FOR select … is not enforced correctly for RECORD users. Instead of hiding the denied elements, the query leaks a subset of them: a deny-all returns the odd-indexed elements, and a per-element predicate keeps and...
CVE-2026-48517
MessagePack for C is a MessagePack serializer for C. Prior to 2.5.301 and 3.1.7, MessagePack-CSharp's typeless deserialization includes MessagePackSerializerOptions.ThrowIfDeserializingTypeIsDisallowedType as a safety check for dangerous types. The default implementation checks the outer type nam...
CVE-2026-48517: Use of Externally-Controlled Input to Select Classes or Code
MessagePack for C is a MessagePack serializer for C. Prior to 2.5.301 and 3.1.7, MessagePack-CSharp's typeless deserialization includes MessagePackSerializerOptions.ThrowIfDeserializingTypeIsDisallowedType as a safety check for dangerous types. The default implementation checks the outer type nam...
EUVD-2026-21402
In systemd 260 before 261, a local unprivileged user can trigger an assert via an IPC API call with an array or map that has a null element...
CVE-2025-65570
A type confusion in jsish 2.0 allows incorrect control flow during execution of the OPNEXT opcode. When an “instanceof” expression uses an array element access as the left-hand operand inside a for-in loop, the instructions implementation leaves an additional array reference on the stack rather...
CVE-2025-65570
A type confusion in jsish 2.0 allows incorrect control flow during execution of the OPNEXT opcode. When an “instanceof” expression uses an array element access as the left-hand operand inside a for-in loop, the instructions implementation leaves an additional array reference on the stack rather...
CVE-2025-65570
A type confusion in jsish 2.0 allows incorrect control flow during execution of the OPNEXT opcode. When an “instanceof” expression uses an array element access as the left-hand operand inside a for-in loop, the instructions implementation leaves an additional array reference on the stack rather...
CVE-2025-65570
A type confusion in jsish 2.0 allows incorrect control flow during execution of the OPNEXT opcode. When an “instanceof” expression uses an array element access as the left-hand operand inside a for-in loop, the instructions implementation leaves an additional array reference on the stack rather...