Live › vulnerability › CVE-2026-116489
Go to dashboardTimescale pgvectorscale before 0.9.1 can be made to confuse pgvector's vector type by shadowing it with attacker-created objects in the vectorscale schema. A database user with CREATE privilege on that schema can then build and query DiskANN indexes to trigger out-of-bounds reads and writes, leaking memory, crashing the server, or escalating privileges.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 16:31 UTC. All times on this page are UTC.
Teams running pgvectorscale below 0.9.1 in PostgreSQL, usually alongside pgvector for vector search. Exposure depends on whether non-admin database users hold CREATE privilege on the vectorscale schema, since that is what lets them plant shadowing objects. Systems where only trusted administrators can create objects in the database are much less exposed.
No product ranges from the sources yet.
SELECT extversion FROM pg_extension WHERE extname = 'vectorscale';\dn+ vectorscale in psql0.9.1 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Timescale pgvectorscale before 0.9.1 contains a type confusion vulnerability that allows low-privileged database users to corrupt memory by shadowing pgvector's vector type or operators. Attackers with CREATE privilege on the vectorscale schema can pre-create shadow objects, then build and query DiskANN indexes over crafted values to cause out-of-bounds reads and writes, disclosing memory, crashing the server, or escalating privileges.
This page as .md · .json · in your agent: get_signal("CVE-2026-116489")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.