CVE-2026-70634: TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read in the Dictionary compression…
CVE-2026-70634 · Severity: high · CVSS 8.1 · Published 2026-08-06
TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read in the Dictionary compression reverse row iterator (tsl/src/compression/algorithms/dictionary.c). The forward path validates the decoded index; the reverse path uses an assertion compiled out of release builds, leaving the 64-bit Simple8b index unvalidated and the read offset attacker-controlled. Attackers with DML access to a physical compressed relation can store a crafted datum and run a reverse-order scan. With a pass-by-value column type the out-of-bounds Datum is returned to the client as a normal column value, disclosing backend memory including the shared buffer pool, which SQL access control does not cover.
No. Junglewise Threat Intelligence has no report of CVE-2026-70634 being exploited in the wild.
How severe is CVE-2026-70634?
High severity, with a CVSS score of 8.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-70634?
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-70634?
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.