Fix type confusion with materialized set-returning functions

Set-returning functions in the target list with indeterminate RECORD
return types incorrectly used the same tuple descriptor to read and
return tuples from the tuplestore across invocations.

These types of SRFs resolve their rowtype from the passed in record
argument and it can differ from invocation to invocation. Reading tuples
with the wrong shape of tuple descriptor can lead to incorrect results,
crashes, and security issues. It was reported as a way to read arbitrary
out-of-line values via json_populate_recordset().

To fix this, drop and recreate the slot and its tuple descriptor per SRF
invocation for materialized SRFs in the target list with dynamic RECORD
return types.

Only the target-list path is affected: table functions in FROM validate
every result against the query-supplied descriptor, and value-per-call
SRFs never retain a slot.

Co-authored-by: Melanie Plageman <[email protected]>
Co-authored-by: Robert Haas <[email protected]>
Security: CVE-2026-120141
Backpatch-through: 14

Branch
------
REL_18_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/4fb349500a20105ef476c524efea95e7b1c03a66
Author: Robert Haas <[email protected]>

Modified Files
--------------
src/backend/executor/execSRF.c     | 59 ++++++++++++++++++++++++++++++++------
src/test/regress/expected/json.out | 11 +++++++
src/test/regress/sql/json.sql      |  5 ++++
3 files changed, 67 insertions(+), 8 deletions(-)

Reply via email to