Skip to main content
CVE-2026-14673VulnerabilityPublished

PostgreSQL amcheck · Untrusted Search Path

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-14673· Low 3.8

Not known to be exploited · CVSS 3.8 Low · fixed in 18.6 : update PostgreSQL when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
3.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 18.6, 16.15, 15.19 +2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 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 13 Nov 2026.

What to do

Upgrade PostgreSQL to 18.6, 16.15, 15.19 or 14.24; postgresql/postgresql to 18.5, 16.15, 15.19 or 14.24.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.6
Fixed in
  • 18.6
PostgreSQLAffected
  • >=16 <16.15
Fixed in
  • 16.15
PostgreSQLAffected
  • >=15 <15.19
Fixed in
  • 15.19
PostgreSQLAffected
  • <14.24
Fixed in
  • 14.24
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • <14.24
  • <15.19
  • <16.15
  • <18.5
Fixed in
  • 14.24
  • 15.19
  • 16.15
  • 18.5

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

AI-suggested

Upgrade PostgreSQL to versions 14.24, 15.19, 16.15, or 18.5 or later where this vulnerability is fixed.

Description

A vulnerability in PostgreSQL's amcheck extension allows a user with EXECUTE privilege on the amcheck function to execute arbitrary functions as the owners of expression indexes by setting a malicious search path before invoking the function. This affects PostgreSQL major versions 14, 15, 16, and 18 prior to minor versions 14.24, 15.19, 16.15, and 18.5 respectively. PostgreSQL 17 is not affected.

References

Community reviews

Loading reviews…