Skip to content

← Public intelligence

Go package

go.mongodb.org/mongo-driver

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.9GoPublished

    mongo-go-driver has Heap Out-of-Bounds Read in GSSAPI Error Handling

    CVE-2026-2303 · GHSA-cp6g-7hqx-qxhp

    Affected
    • Go go.mongodb.org/mongo-driver < 1.17.7
    Fixed in
    1.17.7· Vendor fix available
    Issue
    The mongo-go-driver repository contains CGo bindings for GSSAPI (Kerberos) authentication on Linux and macOS. The C wrapper implementation contains a heap out-of-bounds read vulnerability due to incorrect assumptions about string termination in the GSSAPI standard. Since GSSAPI buffers are not guaranteed to be null-terminated or have extra padding, this results in reading one byte past the allocated heap buffer.

    Recommended action: Upgrade to 1.17.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.8GoPublished

    go.mongodb.org/mongo-driver improperly validates cstrings when marshalling Go objects into BSON

    CVE-2021-20329 · GHSA-f6mq-5m25-4r72

    Affected
    • Go go.mongodb.org/mongo-driver < 1.5.1
    Fixed in
    1.5.1· Vendor fix available
    Issue
    Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents. This issue affects all MongoDB GO Drivers up to (and including) 1.5.0.

    Recommended action: Upgrade to 1.5.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →