CVE-2026-116328 · Runtime
NO FIX YET · SEE WHAT TO DO
PostgreSQL's generation memory contexts have an integer wraparound bug triggered by freeing an allocation over 1 GB. A database user can use it to execute arbitrary code as the operating system user running the database.
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.
Any server running PostgreSQL 16, 17, or 18 below the patched minor versions is exposed, and the attacker must already hold a database login. Servers running PostgreSQL 15 or earlier are not affected, per the sources. Teams using managed database services should wait for the provider to apply the patch.
Not affected if managed-hosting-patched, postgresql-15-or-older
Who cares database, postgresql, self-hosted
SELECT version(); in psql and compare the version against the affected rangespostgres --version18.7, 17.12, and 16.1618.7 or later17.12 or laterInteger wraparound in PostgreSQL generation memory contexts allows a database user to execute arbitrary code as the operating system user running the database, via freeing an allocation larger than 1 GB and causing its block to be reused for smaller chunks whose back-pointer offset cannot represent that position. Within major versions 16-18, minor versions before PostgreSQL 18.7, 17.12, and 16.16 are affected. Versions before PostgreSQL 16 are unaffected.
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.
16.16 or later