CVE-2026-2303
Awaiting Analysis Awaiting Analysis - Queue
Heap Out-of-Bounds Read in mongo-go-driver GSSAPI C Wrapper

Publication date: 2026-02-10

Last updated on: 2026-02-10

Assigner: MongoDB, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-10
Last Modified
2026-02-10
Generated
2026-06-16
AI Q&A
2026-02-10
EPSS Evaluated
2026-06-14
NVD
CVE-2026-2303
EUVD
EUVD-2026-7065
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mongodb mongo-go-driver *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-183 The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are explicitly allowed by policy because the inputs are assumed to be safe, but the list is too permissive - that is, it allows an input that is unsafe, leading to resultant weaknesses.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the mongo-go-driver repository, specifically in the CGo bindings for GSSAPI (Kerberos) authentication on Linux and macOS. The issue arises from a heap out-of-bounds read caused by incorrect assumptions about string termination in the GSSAPI standard. Since GSSAPI buffers are not guaranteed to be null-terminated or padded, the code reads one byte beyond the allocated heap buffer, leading to a potential memory safety issue.

Impact Analysis

The vulnerability can lead to an out-of-bounds read on the heap, which may cause information disclosure or memory corruption. According to the CVSS v3.1 score, it has a base score of 6.5 with a high impact on integrity but no impact on confidentiality or availability. This means an attacker with low privileges could potentially manipulate data integrity without user interaction, possibly affecting the reliability of the authentication process.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2303. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart