CVE-2026-14673: PostgreSQL · Untrusted Search Path
Affects PostgreSQLSource CVE Database V5
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
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in PostgreSQL versions 14.24, 15.19, 16.15, and 18.6. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation steps are indicated.
Description
CVE-2026-14673 is a low-severity vulnerability in PostgreSQL affecting certain minor versions of major releases 14, 15, 16, and 18. It involves an untrusted search path issue in the amcheck extension, where a user with EXECUTE privilege on the amcheck function can execute arbitrary functions as owners of expression indexes by manipulating the search path. PostgreSQL 17 is not affected.