diff --git a/changelog/16.0/16.0.8/summary.md b/changelog/16.0/16.0.8/summary.md
new file mode 100644
index 00000000000..947aabd3f68
--- /dev/null
+++ b/changelog/16.0/16.0.8/summary.md
@@ -0,0 +1,25 @@
+## Summary
+
+### Table of Contents
+
+- **[Major Changes](#major-changes)**
+  - **[Breaking Changes](#breaking-changes)**
+    - [ExecuteFetchAsDBA rejects multi-statement SQL](#execute-fetch-as-dba-reject-multi)
+
+## <a id="major-changes"/>Major Changes
+
+### <a id="breaking-changes"/>Breaking Changes
+
+#### <a id="execute-fetch-as-dba-reject-multi"/>ExecuteFetchAsDBA rejects multi-statement SQL
+
+`vtctldclient ExecuteFetchAsDBA` (and similarly the `vtctl` and `vtctlclient` commands) now reject multi-statement SQL with error.
+
+For example, `vtctldclient ExecuteFetchAsDBA my-tablet "stop replica; change replication source to auto_position=1; start replica` will return an error, without attempting to execute any of these queries.
+
+Previously, `ExecuteFetchAsDBA` silently accepted multi statement SQL. It would (attempt to) execute all of them, but:
+
+- It would only indicate error for the first statement. Errors on 2nd, 3rd, ... statements were silently ignored.
+- It would not consume the result sets of the 2nd, 3rd, ... statements. It would then return the used connection to the pool in a dirty state. Any further query that happens to take that connection out of the pool could get unexpected results.
+- As another side effect, multi-statement schema changes would cause schema to be reloaded with only the first change, leaving the cached schema inconsistent with the underlying database.
+
+`ExecuteFetchAsDBA` does allow a specific use case of multi-statement SQL, which is where all statements are in the form of `CREATE TABLE` or `CREATE VIEW`. This is to support a common pattern of schema initialization.
diff --git a/changelog/16.0/README.md b/changelog/16.0/README.md
index 86fd6e15961..49840b049bb 100644
--- a/changelog/16.0/README.md
+++ b/changelog/16.0/README.md
@@ -1,5 +1,7 @@
 ## v16.0
 The dedicated team for this release can be found [here](team.md).
+* **[16.0.8](16.0.8)**
+
 * **[16.0.7](16.0.7)**
 	* [Changelog](16.0.7/changelog.md)
 	* [Release Notes](16.0.7/release_notes.md)