CVE-2026-116336 · Runtime
NO FIX YET · SEE WHAT TO DO
A flaw in PostgreSQL's REINDEX CONCURRENTLY handling of dropped indexes lets a user who can create database objects run arbitrary code as the operating system user running the database. The sources say an attacker does this through an index expression that issues DROP INDEX.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Versions of PostgreSQL before 18.7, 17.12, 16.16, 15.20 and 14.25 are affected. The attacker needs to be able to create objects in the database, so databases with only trusted users are at lower risk. Look at any server running PostgreSQL that accepts object creation from less-trusted accounts.
Not affected if fixed-version, trusted-users-only
Who cares database, postgresql, self-hosted
SELECT version(); in psql and compare against the fixed versions.18.717.1216.1615.2014.25Operation on a dropped index in PostgreSQL REINDEX CONCURRENTLY allows an object creator to execute arbitrary code as the operating system user running the database, via an index expression that issues DROP INDEX. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.