cve.bz

CVE-2026-116325 PostgreSQL reindexdb index name quoting allows SQL injection

8.0 highEPSS 0.4%

High (8.0). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
SQL injection in PostgreSQL reindexdb allows an object creator to execute arbitrary SQL as the database user running reindexdb, via a crafted index name embedded in the parallel catalog query for --jobs with --index. Within major versions 17-18, minor versions before PostgreSQL 18.7 and 17.12 are affected. Versions before PostgreSQL 17 are unaffected.

Severity

CVSS 3.1

8.0 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
PostgreSQL (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-116325 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116325?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116325?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116325 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-116325

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-116325](https://cve.bz/cve/badge/CVE-2026-116325.svg)](https://cve.bz/cve/CVE-2026-116325)

HTML:

<a href="https://cve.bz/cve/CVE-2026-116325"><img src="https://cve.bz/cve/badge/CVE-2026-116325.svg" alt="CVE-2026-116325"></a>

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12postgresql-15no fix listedDEBIAN-CVE-2026-116325
Debian13postgresql-1717.12-0+deb13u1DEBIAN-CVE-2026-116325
Debian14postgresql-18no fix listedDEBIAN-CVE-2026-116325
Ubuntu20.04:LTSpostgresql-12no fix listedUBUNTU-CVE-2026-116325
Ubuntu22.04:LTSpostgresql-14no fix listedUBUNTU-CVE-2026-116325
Ubuntu24.04:LTSpostgresql-16no fix listedUBUNTU-CVE-2026-116325
Ubuntu26.04:LTS, 26.10postgresql-18no fix listedUBUNTU-CVE-2026-116325
UbuntuPro:14.04:LTSpostgresql-9.3no fix listedUBUNTU-CVE-2026-116325
UbuntuPro:16.04:LTSpostgresql-9.5no fix listedUBUNTU-CVE-2026-116325
UbuntuPro:18.04:LTSpostgresql-10no fix listedUBUNTU-CVE-2026-116325
Red Hathummingbird:1libpq, libpq-devel0:18.7-0.1.hum1RHSA-2026:99821
Alpinev3.21, v3.22postgresql1515.20-r0ALPINE-CVE-2026-116325
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1616.16-r0ALPINE-CVE-2026-116325
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1717.12-r0ALPINE-CVE-2026-116325
Alpinev3.23, v3.24postgresql1818.7-r0ALPINE-CVE-2026-116325

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as having an Important impact because an authenticated user with object creation privileges can escalate permissions to execute arbitrary SQL commands under the administrative identity running maintenance tasks. Exploitation requires an administrator to run the reindexdb utility specifying both parallel worker jobs and individual index targets against a database containing malicious index names. PostgreSQL deployments on versions prior to 17 do not include parallel catalog query logic in this utility and are not affected.

Red Hat's mitigation

Avoid combining parallel execution with index targeting when running the reindexdb utility, or invoke reindexing operations directly via SQL.

1. Execute reindexdb sequentially without the parallel worker flag (`-j` / `--jobs`):

```

reindexdb -d <database_name> --index <index_name>

```

2. Alternatively, perform the reindex operation directly through a psql session:

```

REINDEX INDEX <index_name>;

```

Caveat: Performing index maintenance sequentially instead of concurrently across multiple worker jobs may prolong maintenance tasks on large databases.

ProductPackageStateAdvisory
Red Hat Hardened ImageslibpqAffected
Red Hat Hardened Imagespostgresql17Affected
Red Hat Hardened Imagespostgresql18Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116325.

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON