Last-minute updates for release notes.

Security: CVE-2024-0985 (not CVE-2023-5869 as claimed in prior commit msg)

diff --git a/doc/src/sgml/release-16.sgml b/doc/src/sgml/release-16.sgml
index a380b7d4fadbd09616db25ddd161ebb50f6b2187..fa6dae79b9fb8cf8a2c2265cdc248ef662157d20 100644 (file)
--- a/doc/src/sgml/release-16.sgml
+++ b/doc/src/sgml/release-16.sgml
@@ -41,6 +41,50 @@
 
     
 
+     
+      Tighten security restrictions within REFRESH MATERIALIZED
+      VIEW CONCURRENTLY (Heikki Linnakangas)
+     
+
+     
+      One step of a concurrent refresh command was run under weak security
+      restrictions.  If a materialized view's owner could persuade a
+      superuser or other high-privileged user to perform a concurrent
+      refresh on that view, the view's owner could control code executed
+      with the privileges of the user running REFRESH.
+      Fix things so that all user-determined code is run as the view's
+      owner, as expected.
+     
+
+     
+      The only known exploit for this error does not work
+      in PostgreSQL 16.0 and later, so it may
+      be that v16 is not vulnerable in practice.
+     
+
+     
+      The PostgreSQL Project thanks Pedro
+      Gallegos for reporting this problem.
+      (CVE-2024-0985) 
+     
+    
+
+    
+