timescaledb vulnerabilities and fixes
Recent CVEs affecting timescaledb, with upgrade or downgrade steps. 3 tracked.
timescaledb has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2026-08-06. Highest priority: CVE-2026-70634 (score 39/100).
- CVE-2026-70634 HIGH 8.1 UPGRADE TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read in the Dictionary compress
- CVE-2026-70635 HIGH 7.1 UPGRADE TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read vulnerability that allows
- CVE-2026-70633 MEDIUM 6.5 UPGRADE TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read vulnerability in the Goril
FAQ
How do I fix timescaledb vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is timescaledb being exploited right now?
None of the tracked timescaledb CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which timescaledb CVE should I patch first?
CVE-2026-70634 currently ranks highest (39/100): TimescaleDB through 2.29.1, fixed in commit 517c13e, contains an out-of-bounds read in the Dictionary compress.