CVE-2026-70635: TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read vulnerability that allows…
CVE-2026-70635 · Severity: high · CVSS 7.1 · Published 2026-08-06
TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read vulnerability that allows authenticated attackers to cause query-result integrity failures or backend crashes by supplying a crafted Simple8b selector-11 value, which is stored in the signed int16 Arrow dictionary-index type and bypasses index validation checks in bulk text dictionary decompression. Attackers with direct DML access to a non-frozen physical compressed hypertable relation can trigger an out-of-bounds read before the base of the live offsets array through the VectorAgg single-text hashing strategy, resulting in incorrect aggregation output, backend SIGSEGV, or PostgreSQL crash recovery depending on build configuration.
No. Junglewise Threat Intelligence has no report of CVE-2026-70635 being exploited in the wild.
How severe is CVE-2026-70635?
High severity, with a CVSS score of 7.1, published 6 August 2026.
Which products and versions are affected?
Timescaledb. The advisory does not name versions.
Is there a fix for CVE-2026-70635?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-70635?
Check whether you run Timescaledb. 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.