CVE-2026-116321 · Runtime
NO FIX YET · SEE WHAT TO DO
PostgreSQL does not null-terminate a fixed-length name value after array element assignment, so a database user can make code read past the value. An attacker with database access can disclose server memory.
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 PostgreSQL server on a version before 18.7, 17.12, 16.16, 15.20 or 14.25 is affected. The attacker must be a database user who can run SQL, so exposure depends on who holds database accounts. Servers where only trusted application roles can connect are at lower risk.
Not affected if no-untrusted-db-users, patched-version
Who cares managed-database, postgresql, self-hosted
SELECT version(); in psql and compare against the fixed releases below.18.7, 17.12, 16.16, 15.20, or 14.25.18.717.12Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via changing the final byte of a fixed-length name value to a nonzero byte and passing it to code that treats the value as a C string. 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:L/I:N/A:N
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.1615.2014.25