Christophe Pettus: pgvector 0.8.2 and the Trouble With Parallel HNSW
pgvector 0.8.2 has been released to address a critical buffer overflow vulnerability in parallel HNSW index builds. Users are advised to upgrade to this version to prevent potential data leaks or crashes. The issue arises from the complexities of shared memory management during parallel builds, which can lead to corruption across different user sessions.
- ▪pgvector 0.8.2 fixes CVE-2026-3172, a heap buffer overflow in parallel HNSW index builds.
- ▪The vulnerability can leak data from other relations or crash the database server.
- ▪Users should upgrade to pgvector 0.8.2 and check their managed provider's version to ensure they are protected.
Planet PostgreSQL files mainly under programming. We currently carry 28 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Postgr |
| Canonical URL | https://postgr.es/p/9jJ |
| Publication time | Fri, 22 May 2026 15:00:00 +0000 |
| Retrieval time | 2026-05-22T15:02:02.404Z |
| Last seen | 2026-05-22T15:02:02.404Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | zpJz-axLtYTd |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
2026-05-22 4 min PostgreSQL pgvector 0.8.2 and the Trouble With Parallel HNSW pgvector 0.8.2 is out. It fixes CVE-2026-3172, a heap buffer overflow in parallel HNSW index builds that can leak data from other relations or crash the backend. If you run pgvector and have it pinned to a version below 0.8.2, upgrade. If you are on a managed provider, check which pgvector version they actually ship — a non-trivial number of them lag the upstream release by weeks, and “we support pgvector” does not mean “we are on the version that fixed the parallel HNSW bug.” What broke HNSW is a layered graph.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Postgr.
Discussion
0 commentsMore from Postgr
