# CVE-2026-120144: PostgreSQL type-cache invalidation arbitrary code execution

Source: https://junglewise.ai/threats/cve-2026-120144-type-confusion-from-incomplete-postgresql-type-cache  
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-120144 · Severity: high · CVSS 8.8 · Published 2026-11-12

PostgreSQL, a widely-used database server, contains a flaw in how it manages internal caches for data types. An attacker with database object creation privileges can exploit incomplete cache invalidation to achieve arbitrary code execution with the privileges of the database system user. This allows unauthorized access, data modification, or system compromise.

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

## Quick answers

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

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

**Which products and versions are affected?** PostgreSQL 18.0 through 18.6.

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

**How is CVE-2026-120144 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-120144?** 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

## Technical details

Type confusion vulnerability in PostgreSQL's type-cache invalidation mechanism arises when a composite type is modified while its cache entry is being populated, allowing an object creator to trigger arbitrary code execution as the operating system user. The attack requires authenticated database access (CREATE OBJECT privilege). PostgreSQL 18.x before 18.7 is affected; versions before 18 are unaffected.

## Affected products

- PostgreSQL PostgreSQL 18.0 through 18.6

## Timeline

- 2026-11-12: disclosed
- 2026-11-12: patched

## References

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

## 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)