Untrusted search path in PostgreSQL amcheck allows a grantee of amcheck function EXECUTE privilege to execute arbitrary functions as the owners of expression indexes that depend on the search path, via setting a hostile search path before calling the amcheck function. Within major versions 18, 16, 15, and 14, minor versions before PostgreSQL 18.6, 16.15, 15.19, and 14.24 are affected. PostgreSQL 17 is unaffected.
CVE-2026-14673
Score 3.8 from GitHub Security Advisory (severity: LOW) published 2026-08-13. a secondary CVSS source baseline 3.8; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 3.8
- EG Score
- 3.8(medium)
- EG Risk
- 17(Track)EG Risk 17/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity38% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 29, 2026
References (1)
- f86ef6dc-4d3a-42ad-8f28-e6d5547a5007https://www.postgresql.org/support/security/CVE-2026-14673/
Vendor Advisories for CVE-2026-14673(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:57198Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:54751Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- GHSA-qp83-ppf3-v924GitHub Security AdvisoriesLow
Untrusted search path in PostgreSQL amcheck allows a grantee of amcheck function EXECUTE...
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | postgresql-server-dev-16 (16.15-0ubuntu0.24.04.1) @ noble | 2026-09-17 | ubuntu |
| redhat | postgresql17-main-17.11-1.hum1 | 2026-08-20 | redhat |
| redhat | postgresql18-main-18.6-0.1.hum1 | 2026-08-13 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(11 across 7 ecosystems)
Alpine:v3.21(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql16 | — | 16.15-r0 | — |
| postgresql17 | — | 17.11-r0 | — |
Alpine:v3.22(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql16 | — | 16.15-r0 | — |
| postgresql17 | — | 17.11-r0 | — |
Alpine:v3.23(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql17 | — | 17.11-r0 | — |
| postgresql18 | — | 18.5-r0 | — |
Alpine:v3.24(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql17 | — | 17.11-r0 | — |
| postgresql18 | — | 18.5-r0 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql-15 | 15.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions) | 15.19-0+deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql-17 | 17.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions) | 17.11-0+deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql-18 | 18.0-1 ... 18~~devel.20250502-1 (20 versions) | 18.6-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(2)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 11× in last 7d / 54× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-17 01:52 UTCEG score recompute
- 2026-09-17 01:52 UTCVendor advisory
- 2026-09-17 01:52 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-14 01:33 UTCEG score recompute
- 2026-09-14 01:33 UTCVendor advisory
- 2026-09-14 01:33 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-11 01:14 UTCEG score recompute
- 2026-09-11 01:14 UTCVendor advisory
- 2026-09-11 01:14 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-08 00:55 UTCEG score recompute
- 2026-09-08 00:55 UTCVendor advisory
- 2026-09-08 00:55 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-05 00:35 UTCEG score recompute
- 2026-09-05 00:35 UTCVendor advisory
Show 45 moreShow fewer
- 2026-09-05 00:35 UTCGHSA enrichment
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-01 23:45 UTCEG score recompute
- 2026-09-01 23:45 UTCVendor advisory
- 2026-09-01 23:45 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:26 UTCEG score recompute
- 2026-08-29 23:26 UTCVendor advisory
- 2026-08-29 23:26 UTCGHSA enrichment
- 2026-08-29 23:14 UTCEG score recompute
- 2026-08-29 23:14 UTCVendor advisory
- 2026-08-29 23:14 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 02:18 UTCEG score recompute
- 2026-08-28 02:18 UTCVendor advisory
- 2026-08-28 02:18 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 01:57 UTCEG score recompute
- 2026-08-25 01:57 UTCVendor advisory
- 2026-08-25 01:57 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 01:39 UTCEG score recompute
- 2026-08-22 01:39 UTCVendor advisory
- 2026-08-22 01:39 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 01:20 UTCGHSA enrichment
- 2026-08-18 15:33 UTCEG score recompute
- 2026-08-18 15:33 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-16 16:49 UTCEG score recompute
- 2026-08-16 16:49 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-13 16:30 UTCEG score recompute
- 2026-08-13 16:30 UTCGHSA enrichment
- 2026-08-13 16:02 UTCEG score recompute
- 2026-08-13 16:02 UTCGHSA enrichment
- 2026-08-13 13:17 UTCEG score recompute
- 2026-08-13 13:16 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p99HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p96HIGH
Same CWE
10 shownCWE-426
Frequently asked(5)
What is CVE-2026-14673?
When was CVE-2026-14673 disclosed?
Is CVE-2026-14673 actively exploited?
What is the CVSS score of CVE-2026-14673?
How do I remediate CVE-2026-14673?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14673
Is Your Infrastructure Affected by CVE-2026-14673?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.