Known Issues
5279 tracked MongoDB server issues from Jira with status, affected versions, and resolution details.
GODRIVER-4051Backlog
Add a copy of the Go compatibility guarantee to fix bugs to mongo/doc.go
h3. *Context*
The Go driver should reserve the right to fix bugs, even if users depend on them. However, this should be done judiciously.
h3. *Definition of done*
Copy the following from the [Go compatibility guarantee|https://go.dev/doc/go1compat] into mongo/doc.go:
{quote}
The MongoDB Go Driver follows [semantic versioning|https://semver.org/] for its releases. However, if a compiler or library has a bug that violates the specification, a program that depends on the buggy behavior may
Components
Docs
GODRIVER-3619Backlog
-------HORIZON MARKER-------
This ticket is a marker ticket for planning purposes.
GODRIVER-4027ClosedDuplicate
Update to libmongocrypt 1.21.0
h3. *Context*
{color:#505f79}Describe the background behind the problem.{color}
h3. *Definition of done*
* Update libmongocrypt to v1.21.0
* Remove "uv" override of the "cmake" dependency [here|https://github.com/mongodb/mongo-go-driver/blob/25724e5ddec775c78be6a4794279068f3de03b1e/etc/install-libmongocrypt.sh#L44].
* Remove TODO comment [here|https://github.com/mongodb/mongo-go-driver/blob/25724e5ddec775c78be6a4794279068f3de03b1e/etc/install-libmongocrypt.sh#L6-L7].
h3. *Pitfalls*
{c
Components
Build
GODRIVER-3743Backlog
Investigate if docker image for compile test can be created and pulled outside of test execution
h3. *Context*
In GODRIVER-3573 an image is created from this [Dockerfile|https://github.com/mongodb/mongo-go-driver/blob/62be27e3f6970353300465444c0a4b4f09a420b2/Dockerfile] to test compilation of the driver over multiple versions and variants. The image is [built then run |https://github.com/mongodb/mongo-go-driver/blob/62be27e3f6970353300465444c0a4b4f09a420b2/internal/test/compilecheck/compile_check_test.go#L127-L132]on ever execution of the test. But this image should not change very often
GODRIVER-3881Backlog
-------PRIORITIZATION MARKER-------
This ticket is a marker ticket for planning purposes.
GODRIVER-3599Blocked
Automate SBOM generation using CycloneDX tools for Client Libraries
h3. *Summary*
A recent evaluation (as of Jun 6, 2025) of SBOM coverage indicates that some client libraries (.NET, Node, Python, Go, PHP, Ruby, Rust, Java) have static SBOMs without any components defined. Our client libraries generally do not bundle third-party dependencies, but instead end-users make use of the ecosystem's package manager to install any dependencies.
h3. *Motivation*
As we seek to improve the coverage of our third party vulnerability management, we’d like to raise the
GODRIVER-3879Backlog
Process or automation for confirming tickets are included in patch releases
h3. *Context*
Currently we use a Github webhook to post comments on Jira tickets when they're merged into specific branches. That allows us to audit which tickets are included in which branch, which is most useful when doing patch releases. That process has some issues:
* The webhook must be updated each time there's a new minor version because of the way the webhook service works (https://github.com/10gen/githook).
* We recently lost access to modify the Github webhooks, meaning that what wa
GODRIVER-3629Backlog
Create PR workflow that warns about branch strategy for bug-labeled tickets
It's really easy to forget the merge priority rules when resolving a bug. Now that we are required to label a PR with bug / feature / etc, we should consider creating a followup hook that warns bug-labeled PRs if they are pointing at the master branch -- more than likely they should be pointing at release/X.Y.
Additionally, we could consider adding a checklist to the PR description for contributors to acknowledge if (1) they are working on a bug, and (2) if they are merging into the correct
GODRIVER-3742Backlog
Avoid improper marshal/unmarshal of ReadConcern & WriteConcern
h3. *Context*
Currently the driver allows marshaling the WriteConcern struct but doesn’t convert the Journal struct member to `j` … which can produce an invalid `writeConcern` BSON document.
This is important because users who call RunCommand() are fairly likely to do something like:
… which right now _happens_ to work, but if there’s anything in the WriteConcern.Journal field then an invalid BSON document will result. (I believe WTimeout is also improperly marshaled since it’s a Duration
Components
BSONRead and Write Concern
GODRIVER-3751Backlog
Add MongoDB Atlas Vector Search plugin for Firebase Genkit Go SDK
h3. Summary
[firebase/genkit|https://github.com/firebase/genkit] is an OSS framework for building AI-powered apps in JS, Go, and Python. Used in production by Google’s BaaS, [Firebase|https://firebase.google.com/firebase-and-gcp].
Create a Genkit Go plugin that integrates MongoDB Atlas Vector Search as a vector store for RAG applications, implementing the [ai.Embedder|https://pkg.go.dev/github.com/firebase/genkit/go@v1.3.0/ai#Embedder] and [ai.Retriever|https://pkg.go.dev/github.com/firebase
Components
AI/ML
GODRIVER-3026Backlog
Optimize Collection.insert()
The proposed solution for GODRIVER-2582 involves using reflection. This is very inefficient and non-idiomatic. A more optimized solution would be to defer the logic for parsing the document interface to the collection.insert method. The idea would be to marshal the documents in one operation like this:
Here is a script:
{code}
package benchmark
import (
"reflect"
"testing"
"go.mongodb.org/mongo-driver/bson"
"go.mongodb.org/mongo-driver/bson/bsontype"
)
func reflecti
Components
CRUD
GODRIVER-3746Backlog
Add option to infer BSON unmarshal type based on top-level input type
h2. Context
Starting with Go Driver v2, the BSON library always unmarshals to {{bson.D}} if there is no Go type information provided, including top-level documents and nested documents (GODRIVER-2819). While that solves the problems introduced by the inherently buggy "ancestor" logic (see GODRIVER-2407), it can also silently change the decoded type of nested documents when migrating from v1 to v2 (e.g. GODRIVER-3689, GODRIVER-3576). While users can configure a {{mongo.Client}} or {{bson.Decod
Components
BSON
GODRIVER-3737Backlog
Delay AbortTransaction if the callback returns a timeout error in WithTransaction
h3. *Context*
{{WithTransaction}} always runs {{abortTransaction}} if the transaction callback returns an error and has run at least one operation. However, the {{abortTransaction}} operation can fail if the first transaction operation times out shortly after sending the operation. In that case, {{abortTransaction}} can fail with an error like:
After {{abortTransaction}} returns the above error, it's possible that the transaction may actually have been started on the server and will then rem
Components
Transactions
GODRIVER-3736Backlog
[2.8.0 or later] Move session implementation to internal package
h3. *Context*
Currently, the internal session implementation is located in /x/mongo/driver/session, which is technically accessible to users despite being experimental. According to the MongoDB Driver Sessions Specification, ServerSession (our session.Client) is explicitly described as "an implementation detail and does not need to be public."
The public mongo.Session type correctly implements the spec-required ClientSession interface, but the underlying implementation should be moved to a
Components
Sessions
GODRIVER-3660Backlog
Investigate changes in SERVER-109626: Adjust behavior for emitting additional fields in change streams
This ticket was split from {{DRIVERS-3278}}, please see that ticket for a detailed description.
Components
Change Streams
GODRIVER-3450Backlog
Improve pooled buffer reuse pattern
h3. *Context*
There are some cases where the pooled buffer behavior is unexpected:
* {{bytes.Buffer}} is always initialized with at least 64 bytes. If only values smaller than half of that (32 bytes) are marshaled, buffers will never be reused because of the buffer used capacity check (see [here|https://github.com/mongodb/mongo-go-driver/blob/a9eddec0e7cf4cf37b504d220a33226a3c28bf72/bson/marshal.go#L72] and [here|https://github.com/mongodb/mongo-go-driver/blob/a9eddec0e7cf4cf37b504d220a33226a3
NODE-7416Blocked
Support MongoDB OIDC Built-in Authentication for access to MongoDB with AWS Principals
This ticket was split from {{DRIVERS-3372}}, please see that ticket for a detailed description.
Components
Authentication
SERVER-134780ClosedFixed
Implement POA backpressure on total in-flight batches and bytes
The in-flight batch signal is POA's main backpressure signal: the dispatcher blocks when the dispatched-but-unpopped in-flight batch count or their total bytes of ops exceed a threshold (e.g., 1 GB of in-flight ops). Since a batch is only popped from the inflight FIFO once all of its workers complete, a single slow worker naturally holds its batches in the FIFO queue. Tracking bytes alongside the count also bounds the total memory held by dispatched-but-unapplied ops. A per-worker queued-bytes c
Fixed Versions
9.1.0-rc0
GODRIVER-2183Ready for Work
Socks5 Proxy Support
This ticket was split from DRIVERS-1357, please see that ticket for a detailed description.
SERVER-138312ClosedFixed
Require prebuilt cryptography wheels and sandbox Python build caches
h2. Problem
Native RHEL 10 s390x {{archive_dist_test}} can build cryptography from source even though a compatible hosted wheel is pinned in the root lock. The v9.0 rules_poetry importer skips URL-source variants and reads {{marker}} instead of Poetry 2.1's {{markers}}, so pip does not receive the hosted s390x artifact.
The resulting PEP 517 build resolves build-backend dependencies outside the application lock and can invoke maturin/puccinialin. Recent platformdirs rejects relative {{HOME=.}}
Fixed Versions
9.1.0-rc09.1.0-rc10259.0.7