Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
SERVER-138197ClosedDone
Build a mongotune policy that engages CRL based on CPU overload warning signs
SERVER-138939ClosedFixed
Potential null pointer dereference in getRetryableWriteTransactionParticipantCatalog()
I found a potential null pointer dereference in {{getRetryableWriteTransactionParticipantCatalog()}} in MongoDB 8.0.9:
[https://github.com/mongodb/mongo/blob/r8.0.9/src/mongo/db/transaction/transaction_participant.cpp#L155-L162]
In this method, the return value of {{OperationContextSession::get(opCtx)}} is passed to another overload of {{getRetryableWriteTransactionParticipantCatalog()}} without a prior null check:
{{auto session = OperationContextSession::get(opCtx);
return getRetryab
Affected Versions
8.0.9
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-138505Open
Replicated fast count overcounts documents after transition to dedicated CSRS and back to embedded CSRS + restart
*Issue*
The following sequence causes replicated fast count to go out of sync with the actual count and fail collection validation:
# Start a sharded DSC sharded cluster with a embedded CSRS ("config shard").
# Create a sharded collection "coll" with 1 document on the CSRS.
# Force a checkpoint and ensure fast count is flushed.
# Transition the CSRS from embedded to dedicated.
** This moves all data out of the CSRS, and drops "coll" from the CSRS.
# Transition the CSRS back from d
Affected Versions
9.1.0-rc0
SERVER-135763In Code Review
Investigate excluding off-CPU time from interrupt delinquency metrics and instead tracking it in a separate metric
* `$regex` is occasionally delinquent due to spending large amounts of time descheduled. Under contention (for example, 10 runnable threads, 8 cores), the OS periodically deschedules the thread between regex checks. The overdue-window measurement is pure wall clock, so it does not distinguish between 50ms of work and 50μs of work and 50ms of waiting to be re-scheduled.
NODE-7754Ready for Work
OpenAI Agents SDK TypeScript integration
{panel:bgColor=#fafbfc}
*What it is:* Officially support the OpenAI Agents SDK in Python and JavaScript by implementing MongoDB Atlas as a session/memory backend against the SDK's Session protocol, giving OpenAI-SDK agents durable, queryable conversation and memory state.
{panel}
*Why it matters:* MongoDB's document model is a natural fit for session transcript storage — each session is an arbitrarily nested JSON structure (tool calls, message turns, metadata) that maps directly to a BSON doc
Components
ABX
SERVER-138780Open
Add resumable index build coverage for incremental spilling
Interrupting a build mid-collection-scan with committed-but-unpersisted spill batches is the case the captured resume position must survive: the resumed scan re-adds everything after {{lastSpilledRecordId}} and must not lose keys.
This parameterizes the resumable scan-phase jstests with incremental spilling enabled and asserts no keys are lost via full validate, replicated hashes, and per-key lookups. The knob stays off for resumable builds until these pass.
SERVER-139214ClosedFixed
SBE Blueprint changes for StreamingAggStage
Implement {{SbBlueprintStreamingAgg}} for SBE blueprint, to be used by the SBE stage builder to build {{StreamingAggStage}}.
These changes are required for SERVER-138656, broken out for easier code-review
Fixed Versions
9.1.0-rc09.1.0-rc1026
SERVER-136962In Code Review
Avoid consuming initial sync attempts if we can’t find a valid sync source temporarily
In FCBIS today, if we have failed while running commands on our sync source, we may denylist that node as sync source for 60s. This includes [if we cannot open the backup cursor for a variety of reasons.|https://github.com/10gen/mongo/blob/dea37daf08a59d1f88077c8815b03b5b780a95f3/src/mongo/db/modules/enterprise/src/fcbis/file_copy_based_initial_syncer.cpp#L1050-L1052] One of those reasons includes there is already an open backup cursor on our sync source, since we only allow one backup cursor to
SERVER-98874ClosedFixed
[v5.0] Fix flaky 5.0-specific test
The v5.0-only test file, introduced in SERVER-94839 is flaky. We need to fix it
Fixed Versions
5.0.35
SERVER-120949ClosedFixed
Remove Tag Based FCV Generation
In general we don't want to key logic off of anything that isn't tracked inside of git's history (ex. one commit shouldn't ever result in a different binary today vs tomorrow depending on external sources)
Fixed Versions
9.0.0-rc06.0.305.0.354.4.328.3.97.0.418.0.30
SERVER-126021ClosedFixed
Undefined behavior when inserting data with duplicate field names into timeseries collections
{panel:title=Issue Status as of May 12th, 2026|borderColor=#cccccc|titleBGColor=#6cb33f|bgColor=#eeeeee}
*SUMMARY*
This is a critical fix to address [CVE-2026-8053|https://www.cve.org/CVERecord?id=CVE-2026-8053]. Upgrade to MongoDB 8.3.2, 8.2.9, 8.0.23, 7.0.34, 6.0.28, 5.0.33.
*ISSUE DESCRIPTION AND IMPACT*
An issue in MongoDB Server's time-series collection implementation allows an authenticated user with database write privileges to trigger an out-of-bounds memory write in the mong
Fixed Versions
5.0.336.0.289.0.0-rc07.0.348.2.98.3.28.0.23
SERVER-128125ClosedFixed
Align bsonObjToArray ownership semantics with bsonGetImmutable
bsonObjToArray and bsonGetImmutable are sibling functions in the MozJS BSON binding layer. bsonGetImmutable ensures the BSONObj it works with is owned before creating JS wrappers around it; bsonObjToArray does not apply the same treatment. This inconsistency can lead to incorrect behaviour when operating on sub-document wrappers. Bring bsonObjToArray in line with the established pattern used by bsonGetImmutable.
Affected Versions
8.0.27
Fixed Versions
4.4.316.0.295.0.348.3.48.0.267.0.378.2.128.0.287.0.398.3.7
SERVER-139108In Code Review
Add a monguard option to MongoDFixture
https://docs.google.com/document/d/14VAlo-oYIpwxZX8R4n2uTCdiZ0AA6X_IO_gmJg3Ls-A/edit?tab=t.0#heading=h.lesuvrwdky4q
SERVER-137223ClosedFixed
Remove 'run diskstats' from dbtest/unittests task groups on v4.4 (BF-46815)
h3. Problem
dbtest on all four Windows variants of mongodb-mongo-v4.4 (windows, windows-debug, enterprise-windows, enterprise-windows-inmem) system-fails on every activated run since 2026-08-31. No tests fail; the failing command is the *"run diskstats"* background monitor (task step 2).
h3. Root cause
"run diskstats" (function defined at etc/evergreen.yml:751 @ 241f229ba7) runs on Windows:
The command has no working_dir, so mongo-diskstats.csv is written into the agent's host-persistent s
Fixed Versions
4.4.32
SERVER-115508ClosedFixed
Make minimally sized buffers for uncompressed Messages
{panel:title=Issue Status as of Dec 29 2025|borderColor=#cccccc|titleBGColor=#6cb33f|bgColor=#eeeeee}
*SUMMARY*
This is a critical fix to address [CVE-2025-14847|https://www.cve.org/CVERecord?id=CVE-2025-14847]. Upgrade to 8.2.3, 8.0.17, 7.0.28, 6.0.27, 5.0.32, or 4.4.30.
*ISSUE DESCRIPTION AND IMPACT*
An client-side exploit of the Server's zlib implementation can return uninitialized heap memory without authenticating to the server. We strongly recommend upgrading to a fixed version
Fixed Versions
4.4.305.0.326.0.278.2.38.0.177.0.28
SERVER-86363ClosedFixed
Make container registry login silent
Fixed Versions
7.2.17.0.66.0.148.0.0-rc07.3.0-rc3
SERVER-87567ClosedFixed
The SessionWorkflow should correctly return a response error on malformed requests
Fixed Versions
8.0.0-rc05.0.266.0.157.0.77.3.0-rc5
SERVER-88212ClosedFixed
Collect recent perf data on v4.4
Merge three empty commit on v4.4 to collect recent perf data.
The related PERF ticket is https://jira.mongodb.org/browse/PERF-5249
SERVER-85368ClosedFixed
Updates the genny module in sys-perf to point to mongo/genny instead of 10gen/genny
[https://github.com/10gen/genny] redirects to [https://github.com/mongodb/genny.|https://github.com/mongodb/genny] Sys-perf still points to the 10gen/genny repo. This causes the project trigger to not pick up the correct module version for versions triggered from the Genny repo.
This ticket is to update the module definition in sys-perf to mongodb/genny.
Fixed Versions
6.0.157.0.85.0.278.1.0-rc07.3.2
SERVER-79999ClosedFixed
reduce test code coverage on macos builders
Our macos builders in the CI system run on machines that are not built to handle the FSM workloads and we do not have the same level of build failure diagnostics on macos compared to other productin platforms such as Linux and Windows. It would be nice to revisit the test suites we run on these macos builders and identify suites that we can eliminate from our daily CI test runs.
Fixed Versions
8.0.0-rc06.0.157.0.77.3.0-rc47.0.85.0.27