
pgvector 0.8.7 fixes CVE-2026-103484. Any database user who can create an IVFFlat index can write out of bounds in the backend, which can get you to arbitrary code execution. Every version through 0.8.6 is affected. https://thebuild.com/blog/the-vector-that-lied-about-its-dimensions/ Upgrade. That part’s easy. Christophe Pettus spends the rest of the post on the harder questions, mostly: who can actually reach this in a real deployment, and what does “a user who can create an index” mean when your app has one database role that does everything. I’ll argue for consolidating onto Postgres in most rooms I walk into. This is the invoice that comes with that position. Your attack surface is the union of every extension you installed. Each one has its own release cadence, its own maintainer bandwidth, and its own relationship with the word “soon.” Core Postgres has thirty years of security process behind it. The extension you added in a sprint last spring might have one person with a day job. That’s a tradeoff I’ll still take. It’s not a free one. Do you know the installed version of every extension in your production cluster right now, or are you about to go find out?
Post summary
The text reports CVE-2026-103484 in pgvector, an out-of-bounds write vulnerability leading to RCE, and explicitly directs users to upgrade to pgvector 0.8.7. It also provides broader commentary on extension security risks in PostgreSQL deployments.




