CVE-2026-120152: PostgreSQL · Use After Free
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium · fixed in 18.7 : update PostgreSQL when convenient.
Data as of 12 Nov 2026, 14:35 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 18.7, 17.12, 16.16
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade PostgreSQL to 18.7, 17.12 or 16.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
AI-suggested
Upgrading PostgreSQL to versions 16.16, 17.12, or 18.7 or later will remediate this vulnerability. Users should apply these official fixes to eliminate the use-after-free condition in pg_show_all_settings().
Description
CVE-2026-120152 is a use-after-free vulnerability in PostgreSQL's pg_show_all_settings() function. It allows a database user to read memory contents by loading a module while the function scans custom-variable placeholders that the module replaces and frees. This affects PostgreSQL major versions 16 through 18, specifically versions before 16.16, 17.12, and 18.7. Versions prior to 16 are not affected. The vulnerability has a medium severity with a CVSS score of 4.3.