pgvector 0.8.7 fixes a code-execution bug in vector index builds
Any database user who can create an IVFFlat index could trigger an out-of-bounds write and run code inside Postgres. The extension ships on every major managed Postgres provider.
pgvector 0.8.7, released on 5 October, fixes a buffer overflow in IVFFlat index builds tracked as CVE-2026-103484. Security researchers at Compass Security reported it on 1 October: a database user with permission to create an IVFFlat index can write data out of bounds during the build, corrupting memory inside the Postgres process and potentially executing code there. Every version before 0.8.7 is affected.
pgvector is the de facto vector search extension for Postgres, with over 23,000 stars on GitHub. AWS RDS, Supabase, Google Cloud SQL, Azure Database for PostgreSQL and Neon all bundle it or make it a one-line CREATE EXTENSION vector; away.
Why it matters: this turns “can create an index” into “can run code in the database process.” That matters anywhere less-trusted users or app roles have CREATE privileges and can issue their own DDL — a common setup in RAG pipelines where embeddings land straight in Postgres. Upgrade to 0.8.7 before you next build an IVFFlat index.
The caveat: exploitation needs a database role that can already create indexes, so a single-tenant database with no untrusted DDL access is lower risk. If you’re not sure who holds CREATE on your schemas, that’s worth checking before you decide you’re fine.