# CVE-2026-120150: PostgreSQL use after free in expanded-record domain checks

Source: https://junglewise.ai/threats/cve-2026-120150-use-after-free-in-postgresql-expanded-record-domain-checks  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-12. Updated: 2026-11-12  
License: CC BY 4.0 with a link back

CVE-2026-120150 · Severity: high · CVSS 8.8 · Published 2026-11-12

PostgreSQL is a widely-used open-source database server. A use-after-free flaw in how PostgreSQL validates domain types on composite records allows a database user with object creation privileges to execute arbitrary code with the database server's operating system permissions, potentially compromising the entire system and any data it holds.

Technologies: [PostgreSQL](https://junglewise.ai/threats/technologies/postgresql). Vendors: [PostgreSQL](https://junglewise.ai/threats/vendors/postgresql).

## Quick answers

**Is CVE-2026-120150 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-120150 being exploited in the wild.

**How severe is CVE-2026-120150?** High severity, with a CVSS score of 8.8, published 12 November 2026.

**Which products and versions are affected?** PostgreSQL before 18.7, 17.12, 16.16, 15.20, 14.25.

**Is there a fix for CVE-2026-120150?** Yes: fixed in PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-120150 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-120150?** Check whether you run PostgreSQL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25

## Technical details

A use-after-free vulnerability exists in PostgreSQL's expanded-record domain validation logic. When repeated domain checks are performed over a composite type, a dangling memory-context pointer is reused, leading to memory corruption. The vulnerability requires authenticated database access and object creation privileges to exploit; attackers can trigger arbitrary code execution as the OS user running the database process.

## Affected products

- PostgreSQL PostgreSQL before 18.7, 17.12, 16.16, 15.20, 14.25

## Timeline

- 2026-11-12: disclosed: CVE-2026-120150 published
- 2026-11-12: patched: PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 released

## References

- [https://www.postgresql.org/support/security/CVE-2026-120150/](https://www.postgresql.org/support/security/CVE-2026-120150/)

## Related threats

- [PostgreSQL CREATE EXTENSION arbitrary SQL execution](https://junglewise.ai/threats/cve-2026-6467-uncontrolled-search-path-element-in-postgresql-create-extension)
- [PostgreSQL type confusion in ALTER allows arbitrary code execution](https://junglewise.ai/threats/cve-2026-6460-type-confusion-in-postgresql-allows-an-object-creator-to-execute)
- [PostgreSQL type confusion in SQL-language functions arbitrary code execution](https://junglewise.ai/threats/cve-2026-18447-type-confusion-in-postgresql-sql-language-functions-allows-an)
- [PostgreSQL INSERT ON CONFLICT authorization bypass on auto-updatable views](https://junglewise.ai/threats/cve-2026-16237-improper-protection-in-postgresql-insert-on-conflict-on-auto)
- [PostgreSQL dblink and subscriptions arbitrary file append](https://junglewise.ai/threats/cve-2026-14661-external-control-of-file-name-in-postgresql-dblink-and-create)