Skip to content
Percona Software for MongoDB Documentation
Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Server for MongoDB 8.3.13-4 (2026-10-27)

Installation Upgrade from MongoDB Community

We are pleased to announce Percona Server for MongoDB 8.3.13-4, the drop-in replacement for MongoDB Community Edition. Percona Server for MongoDB supports MongoDB Community protocols and drivers and enhances it with enterprise-grade features for free, helping you meet your organization’s requirements for high availability, reliability, and data security.

Percona Server for MongoDB 8.3.13-4 includes:

Important

Percona Server for MongoDB 8.3.13-4 contains fixes for:

You can find details at the bottom of this page.

Release highlights

General Availability of Percona Server for MongoDB 8.3

Percona Server for MongoDB 8.3.13-4 marks the General Availability (GA) of the 8.3 release series. Previous 8.3 releases were available as a technical preview and intended for testing only. Starting with this release, Percona Server for MongoDB 8.3 is production-ready and fully supported for use in production environments.

Percona Server for MongoDB 8.3.13-4 is now the latest, default and recommended version of Percona Server for MongoDB. It is the most performant and feature-rich version of Percona Server for MongoDB ever released.

MongoDB Database Tools are distributed as a separate tarball

Starting with this release, MongoDB Database Tools (mongodump, mongorestore, mongoexport, mongoimport, and others) are no longer included in the Percona Server for MongoDB binary tarball. If you install Percona Server for MongoDB from tarballs, download the MongoDB Database Tools tarball separately from the Percona Downloads website.

This change aligns the distribution of MongoDB Database Tools with how MongoDB Shell (mongosh) is already distributed. It also allows us to deliver tool updates, including security fixes, independently of the server releases.

If you install Percona Server for MongoDB from RPM or DEB packages, nothing changes for you: MongoDB Database Tools are installed as before.

Upgrade recommendation

Percona Server for MongoDB 8.3.13-4 is the latest recommended version of Percona Server for MongoDB. We recommend upgrading to version 8.3.13-4 to benefit from the backup and checkpoint fixes included in MongoDB 8.3.13.

Known issues

This section describes known issues in Percona Server for MongoDB 8.3.13-4 and their resolution status.

  • SERVER-136961 : If a node has an unclean shutdown for any reason and then restarts to perform a file copy based initial sync, the node crashes each time it restarts and cannot complete initial sync without manual intervention.

    This issue affects Percona Server for MongoDB 8.3.7-1 and later versions.

    To recover a node in a self-managed deployment, do one of the following:

    • Restart the node with the initialSyncMethod parameter set to logical.
    • Delete the contents of the node’s dbPath directory, then restart the node to begin a new file copy based initial sync.

Changelog

Improvement

  • PSMDB-1944: MongoDB Database Tools packages are now built independently of Percona Server for MongoDB packages. This allows tool updates, including security fixes, to be prepared without rebuilding the server packages.

  • PSMDB-2182: Improved telemetry for x.509 certificate authentication. x.509 is used by default for internal authentication between members of replica sets and sharded clusters, so telemetry previously reported it as enabled on almost every instance. Telemetry now reports x.509 usage for client authentication separately from its use for internal cluster authentication.

Bugs fixed

  • PSMDB-2126: Fixed an issue where streaming a backup to Google Cloud Storage through its S3-compatible API failed. The issue was caused by the upgrade of the AWS SDK for C++ to version 1.11.471, which added empty checksum elements to multipart upload requests that Google Cloud Storage rejects.

Improvements and bug fixes from upstream MongoDB

The MongoDB 8.3.13 patch release notes list the following change:

Bugs fixed

  • SERVER-132946 : Heap-use-after-free in $_internalApplyOplogUpdate stage when reading via getMore after aggregate Invocation is destroyed
  • SERVER-130431 : Mark $graphLookup as DiskUseRequirement::kWritesTmpData
  • SERVER-134618 : Fix serialization of constant values in $bucket stage
  • SERVER-131412 : Improve Validation Expression
  • SERVER-131411 : Improve bulkWrite
  • SERVER-127294 : Fixed a race condition in an internal network-interface test.

Security fixes from upstream MongoDB

The severity categories below follow CVSS scores version 4.0.

High severity

MongoDB Server’s collection validation feature may not properly handle certain expressions stored in a validator. In some cases, this can cause the server process to stop running when a document is later inserted. The behavior can occur for authenticated users with write access.

A security issue was discovered in MongoDB mongos (the sharded cluster router) where an authenticated user with readWrite privileges could crash the mongos process by crafting a specially formed aggregation pipeline. The issue leverages an internal aggregation stage that lacks proper authorization checks despite being intended for internal use, allowing a subsequent stage to be forced to execute on the router under conditions it was not designed to handle. This results in an unhandled fatal error that causes the mongos process to immediately abort, resulting in denial of service for all clients routed through the affected mongos instance.

A security issue was discovered in MongoDB mongos (the sharded cluster router) where an authenticated user with readWrite privileges could crash the mongos process by crafting a specially formed aggregation pipeline. The issue leverages an internal aggregation stage that lacks proper authorization checks despite being intended for internal use, allowing a subsequent stage to be forced to execute on the router under conditions it was not designed to handle. This results in an unhandled fatal error that causes the mongos process to immediately abort, resulting in denial of service for all clients routed through the affected mongos instance.

Medium severity

A use-after-free issue in the $_internalApplyOplogUpdate aggregation stage could expose unrelated data from server memory in query results. An authenticated user with read privileges could trigger the issue by combining the stage with a batch size of 0. The server process could also terminate unexpectedly.

An issue in the $bucket aggregation stage could cause constant values to be interpreted as field references during internal query rewriting. Under certain conditions, an authenticated user with read access could receive field values that the query did not intend to return.

Find the full list of changes in the MongoDB 8.3.13 changelog .

Tools packaged with this release

This release includes the following tools:

Tool Base version Release notes
MongoDB Shell (mongosh) 2.13.0 upstream release notes
Mongo Tools 100.19.1 upstream release notes