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.
References
| Link | Resource |
|---|---|
| https://github.com/timescale/timescaledb/commit/517c13e7cc6afadb4a7deaa7a5a5a29065e5b5a3 | Patch |
| https://github.com/timescale/timescaledb/pull/10360 | Issue Tracking Patch |
| https://www.vulncheck.com/advisories/timescaledb-out-of-bounds-read-information-disclosure-via-dictionary-compression-reverse-iterator | Patch Third Party Advisory |
Configurations
History
No history.
Information
Published : 2026-08-06 22:18
Updated : 2026-09-01 15:31
NVD link : CVE-2026-70634
Mitre link : CVE-2026-70634
CVE.ORG link : CVE-2026-70634
JSON object : View
Products Affected
timescale
- timescaledb
