Quick answers
- Is CVE-2026-116489 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116489 being exploited in the wild.
- How severe is CVE-2026-116489?
- High severity, with a CVSS score of 7.5, published 26 October 2026.
- Which products and versions are affected?
- Timescale Pgvectorscale before 0.9.1.
- Is there a fix for CVE-2026-116489?
- Yes: fixed in 0.9.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116489 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116489?
- Check whether you run Timescale Pgvectorscale at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.9.1
Technical details
A type confusion vulnerability in pgvectorscale before 0.9.1 allows low-privileged database users with CREATE privilege on the vectorscale schema to shadow pgvector's vector type or operators. Attackers can pre-create shadow objects and build or query DiskANN indexes over crafted values, causing out-of-bounds reads and writes that lead to memory disclosure, server crashes, or privilege escalation.
Affected products
- Timescale pgvectorscale before 0.9.1
Timeline
- 2026-10-26: disclosed