Skip to main content
VulnerabilityPublished Updated

CVE-2026-29089: timescale timescaledb · Untrusted Search Path

Affects timescale timescaledbSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 2.25.2 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.25.2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade timescaledb and timescale/timescaledb to 2.25.2.

Affected software

ProductAffectedFixed in
timescaletimescaledbAffected
  • >=2.23.0 <2.25.2
Fixed in
  • 2.25.2
GitHubtimescale/timescaledbpkg:github/timescale/timescaledbOther threatsAffected
  • <2.25.2 >=2.23.0
Fixed in
  • 2.25.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade TimescaleDB to version 2.25.2 or later, where the vulnerability is patched. Until upgrading, organizations should audit and restrict schema permissions to ensure that user-writable schemas are not included in the search_path used by PostgreSQL and TimescaleDB. Database administrators should review and harden the search_path configuration to exclude untrusted or user-controlled schemas. Additionally, monitoring and alerting on extension upgrade activities and unusual function creations in user schemas can help detect exploitation attempts. Employing the principle of least privilege for database users and limiting the ability to perform extension upgrades to trusted administrators reduces risk. Regularly applying security patches and maintaining an inventory of TimescaleDB versions in use are also critical steps.

Description

TimescaleDB is a time-series database for high-performance real-time analytics packaged as a Postgres extension. From version 2.23.0 to 2.25.1, PostgreSQL uses the search_path setting to locate unqualified database objects (tables, functions, operators). If the search_path includes user-writable schemas a malicious user can create functions in that schema that shadow builtin postgres functions and will be called instead of the postgres functions leading to arbitrary code execution during extension upgrade. This issue has been patched in version 2.25.2.

References

Community reviews

Loading reviews…