couchbase · RayOffiah · Mar 4, 2026 · Mar 9, 2026 · Mar 9, 2026 · Mar 11, 2026
diff --git a/modules/release-notes/pages/relnotes.adoc b/modules/release-notes/pages/relnotes.adoc
@@ -9,6 +9,9 @@ These release notes are focused on bug fixes and breaking changes.
 
 For information about new features and major improvements made in Couchbase Server 8.0, see xref:introduction:whats-new.adoc[What's New].
 
+include::partial$docs-server-8.0.1-fixes-and-improvements.adoc[]
+include::partial$docs-server-8.0.1-known-issues.adoc[]
+''''
 include::partial$docs-server-8.0.0-fixes-and-improvements.adoc[]
 include::partial$docs-server-8.0.0-breaking-changes.adoc[]
 include::partial$docs-server-8.0.0-known-issues.adoc[]

diff --git a/modules/release-notes/partials/docs-server-8.0.1-fixes-and-improvements.adoc b/modules/release-notes/partials/docs-server-8.0.1-fixes-and-improvements.adoc
@@ -0,0 +1,193 @@
+
+
+
+[#release-801]
+== Release 8.0.1 (March 2026)
+
+Couchbase Server 8.0.1 was released in March 2026.
+This maintenance release contains fixes to issues.
+
+[#dlist-fixed-issues-801]
+== Fixed Issues
+
+
+
+
+[#dlist-fixed-issues-801-cluster-manager]
+=== Cluster Manager
+
+*https://jira.issues.couchbase.com/browse/MB-69026/[MB-69026]*::
+
+Addressed an issue with stuck rebalance email alerts in Couchbase Server.
+
++
+
+This fix resolves problems observed when "Require encryption (TLS)" was configured,
+causing alert failures.
+
+*https://jira.issues.couchbase.com/browse/MB-69650/[MB-69650]*::
+
+A problem was introduced in 7.6.2 where the presence of a Cloud Native Gateway in the cluster would cause issues for services connecting to the cluster manager.
++
+The presence of Cloud Native Gateway no longer causes these issues.
+
+*https://jira.issues.couchbase.com/browse/MB-70441/[MB-70441]*::
+
+The upgrade to Erlang version 26 introduced a change in behavior which requires peer certification when TLS is being used for Alert emails.
+The peer certification introduced with the changes for this ticket uses the trusted CA certificates provided by the operating system.
+
+*https://jira.issues.couchbase.com/browse/MB-70597/[MB-70597]*::
+
+Prior to this fix,
+the `ro_security_admin` role user did not have read access to security related groups via a GET of `/settings/rbac/groups`.
+After this fix,
+`ro_security_admin` will be able to see all groups including the security ones
+
+*https://jira.issues.couchbase.com/browse/MB-70629/[MB-70629]*::
+
+RBAC groups containing security_admin_local,
+security_admin_external,
+or ro_admin roles are not handled correctly on upgrade to 8.0.
+The upgrade handling should replace:
+
++
+
+--
+
+* security_admin_local with security_admin + local_user_admin
+* security_admin_external with security_admin + external_user_admin
+* ro_admin with ro_admin + ro_security_admin
+
+--
+
++
+
+The issue also occurs when restoring users from a backup taken on a release prior to 8.0.
+
++
+
+The workaround for both the upgrade and restore case is to manually correct the affected users after the upgrade/restore completes.
+
+
+
+
+
+
+
+
+
+[#dlist-fixed-issues-801-query-service]
+=== Query Service
+
+*https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]*::
+
+* With multi-collection indexes that contained fields with `include in _all` setting enabled - there was a possibility for false positives to show up for field agnostic (composite field) queries.
+This has been addressed by denying the sargability for such indexes.
+* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes.
+* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed.
+
+*https://jira.issues.couchbase.com/browse/MB-69081/[MB-69081]*::
+
+To retrieve a document's expiration,
+the user had to specify the sub-path explicitly,
+i.e.,
+`META().expiration`.
+A call to the `META()` function without the sub-path would return the default expiration value 0 always which was incorrect.
+
+
++
+
+Now,
+when a user’s query invokes the `META()` function without explicitly specifying the subpath,
+the document's expiration value is returned.
+
+*https://jira.issues.couchbase.com/browse/MB-69083/[MB-69083]*::
+
+Problem:
+
++
+
+A query may return an incorrect result under the following conditions:
+
++
+
+* query contains one or more joins
+* one of the joins involves a sub-query (FROM clause subquery)
+* the FROM clause sub-query has a GROUP BY and/or aggregates
+* the FROM clause sub-query can take advantage of index group/aggregate pushdown
+(this requires an appropriate secondary index)
+* CBO is ON,
+and UPDATE STATISTICS has been run on all keyspaces/indexes involved
+
+*https://jira.issues.couchbase.com/browse/MB-69955/[MB-69955]*::
+
+`CYCLE` was added as a KEYWORD for RECURSIVE WITH’s CYCLE subclause.
++
+This causes a syntax error when a path or subpath’s case-insensitive identifier is named `cycle`  when users upgraded to a version that supported the recursive with feature https://docs.couchbase.com/server/current/n1ql/n1ql-language-reference/with-recursive.html[WITH recursive clause]
++
+This is now handled by allowing `cycle` keyword as a permitted identifier.
+
+*https://jira.issues.couchbase.com/browse/MB-70112/[MB-70112]*::
+
+When a prepared request is made with the  `auto_execute` request parameter set as `true`,
+the request would incorrectly error out with error: `Unrecognizable prepared statement - cause: JSON unmarshalling error: auto_execute did not produce a prepared statement`
++
+In this release the server silently ignores the `auto_execute` request parameter when the request is a prepared request.
+
+
+
+[#dlist-fixed-issues-801-eventing-service]
+=== Eventing Service
+
+*https://jira.issues.couchbase.com/browse/MB-69687/[MB-69687]*::
+
+In version 8.0,
+a security vulnerability was identified in the Cluster Manager when node-to-node encryption is enabled and client certificate authentication is configured as `Hybrid` or `Mandatory`.
+This issue,
+which is not present in releases prior to 8.0,
+could be exposed via the Eventing service,
+potentially allowing a user to select and interact with scopes or collections beyond their assigned RBAC permissions.
+This release (`8.0.1`) resolves the underlying issue in the Cluster Manager to ensure that RBAC enforcement is strictly maintained for services across all mutual TLS (mTLS) configurations.
+
+
+
+
+
+[#dlist-fixed-issues-801-index-service]
+=== Index Service
+
+*https://jira.issues.couchbase.com/browse/MB-69935/[MB-69935]*::
+
+Updated chronology for certain storage API calls to avoid rare corner cases of shard metadata mismatch.
+
+
+
+[#dlist-fixed-issues-801-search-service]
+=== Search Service
+
+*https://jira.issues.couchbase.com/browse/MB-70388/[MB-70388]*::
+
+Fixed an issue where we did not set `docvalues` for `geopoint` fields internally,
+causing it to be computed on demand for every query
+
+
+
+[#dlist-fixed-issues-801-tools]
+=== Tools
+
+*https://jira.issues.couchbase.com/browse/MB-67774/[MB-67774]*::
+
+Added support for Debian 13 (Trixie).
+
+
+*https://jira.issues.couchbase.com/browse/MB-70235/[MB-70235]*::
+
+In 8.0.0 restoring to a 7.6 and below cluster with `--auto-create-buckets`  did not work as we were sending a new setting.
+We now omit the setting depending on the version.
+
+*https://jira.issues.couchbase.com/browse/MB-70255/[MB-70255]*::
+
+Addressed a bug where buckets with cross-cluster versioning enabled (link:https://docs.couchbase.com/server/current/learn/clusters-and-availability/xdcr-enable-crossclusterversioning.html[XDCR enable cross-cluster versioning]) would cause a merge to fail.
+
+
+
diff --git a/modules/release-notes/partials/docs-server-8.0.1-known-issues.adoc b/modules/release-notes/partials/docs-server-8.0.1-known-issues.adoc
@@ -0,0 +1,33 @@
+
+[#known-issues-801]
+== Known Issues
+
+For Couchbase Server 8.0.1 was released in March 2026,
+these are the known issues that aren’t yet resolved.
+
+
+
+
+
+
+
+
+
+[#dlist-known-issues-801-search-service]
+=== Search Service
+
+*https://jira.issues.couchbase.com/browse/MB-70770/[MB-70770]*::
+
+In extremely rare scenarios,
+document deletions may not be consistently reflected in the index.
+As a result,
+a small number of documents that have been successfully deleted from the KV layer may continue to persist in the index as stale entries.
+
++
+
+This condition is highly infrequent and non-deterministic,
+but it can lead to minor discrepancies in document counts between FTS and KV.
+Such inconsistencies are typically limited in scope and involve only a very small number of documents; however,
+they may impact count-based validations or comparisons between the two systems.
+
+