CVE-2026-2303
alloy: go.mongodb.org/mongo-driver: mongo-go-driver has Heap Out-of-Bounds Read in GSSAPI Error Handling
CVE-2026-2303 is fixed in 8 products on 1 platform, first by OPENSUSE-SU-2026:21276-1, released July 8, 2026. It is not reported as exploited. Patch Radar priority: Routine.
Routine
CVSS
n/a
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0031
24th percentile
go.mongodb.org/mongo-driver: mongo-go-driver has Heap Out-of-Bounds Read in GSSAPI Error Handling
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| alloy · opensuse-leap 16.0 | 1.19.2-160000.1.1 | OPENSUSE-SU-2026:22032-1 | Oct 6, 2026 |
| alloy · sles 15.7 | 1.19.2-150700.15.29.1 | SUSE-SU-2026:4408-1 | Oct 1, 2026 |
| alloy · sles 16.0 | 1.19.2-160000.1.1 | SUSE-SU-2026:24148-1 | Oct 6, 2026 |
| apptainer · opensuse-leap 16.0 | 1.5.1-bp160.2.1 | OPENSUSE-SU-2026:21276-1 | Jul 8, 2026 |
| apptainer · sles 15.7 | 1.5.1-150600.4.29.1 | SUSE-RU-2026:2815-1 | Jul 9, 2026 |
| golang-github-prometheus-alertmanager · opensuse-leap 16.0 | 0.33.1-bp160.1.1 | OPENSUSE-SU-2026:22027-1 | Oct 6, 2026 |
| golang-github-prometheus-prometheus · sles 15.7 | 3.13.2-150100.4.40.2 | SUSE-SU-2026:4606-1 | Nov 7, 2026 |
| govulncheck-vulndb · opensuse-leap 16.0 | 0.0.20260727T201416-160000.1.1 | OPENSUSE-SU-2026:21551-1 | Aug 10, 2026 |
| govulncheck-vulndb · sles 16.0 | 0.0.20260727T201416-160000.1.1 | SUSE-SU-2026:23227-1 | Aug 10, 2026 |
| grafana · opensuse-leap 16.0 | 12.4.10-bp160.1.1 | OPENSUSE-SU-2026:22125-1 | Nov 7, 2026 |
| grafana · sles 15.7 | 12.4.10-150200.3.94.3 | SUSE-SU-2026:4600-1 | Nov 7, 2026 |
| squashfuse · sles 15.7 | 0.5.0-150600.3.4.1 | SUSE-RU-2026:2815-1 | Jul 9, 2026 |
| system-user-grafana · sles 15.7 | 1.0.0-150200.5.8.1 | SUSE-SU-2026:4600-1 | Nov 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.