PostgreSQL REINDEX CONCURRENTLY · Operation on a Dropped Index
Source GCVE Database
Not known to be exploited · CVSS 8.8 High · fixed in 18.7 : patch PostgreSQL soon.
Data as of 12 Nov 2026, 16:21 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 8.8 |
|---|
- Patch
- Available – fixed in 18.7, 17.12, 16.16 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 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 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | 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
However, the description states that versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected, implying that upgrading to these versions or later mitigates the vulnerability. Users should upgrade PostgreSQL to at least these fixed versions to remediate the issue. Until patched, restrict object creation privileges to trusted users only.
Description
A vulnerability in PostgreSQL's REINDEX CONCURRENTLY operation on a dropped index allows an object creator to execute arbitrary code as the operating system user running the database. This issue affects versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25. The flaw arises from an index expression that issues DROP INDEX, enabling code execution.