CyberSecBulletin
CVE-2026-116336NVD status: Awaiting Analysis

PostgreSQL: Operation on a Resource after Expiration or Release

Published Updated By the CyberSecBulletin desk

CVE-2026-116336 is a high-severity operation on a resource after expiration or release vulnerability in PostgreSQL, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 18.7, 17.12, 16.16 as the first without the flaw, so updating PostgreSQL to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.64% chance of exploitation within 30 days, higher than 51% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update PostgreSQL to 18.7 or 17.12 or 16.16 or 15.20, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
PostgreSQLPostgreSQL18 up to, but not including, 18.7; 17 up to, but not including, 17.12; 16 up to, but not including, 16.16; 15 up to, but not including, 15.20; before 14.2518.7, 17.12, 16.16, 15.20, 14.25

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

Operation 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Operation on a Resource after Expiration or Release

The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.

More Operation on a Resource after Expiration or Release vulnerabilities (CWE-672)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in PostgreSQL

All PostgreSQL vulnerabilities

Recent Operation on a Resource after Expiration or Release vulnerabilities

Spotted an error? Tell us.