An integer overflow in BSON value-length handling in the MongoDB Go Driver can cause a runtime panic when an application validates or accesses a malformed BSON document. An unauthenticated actor who can supply BSON bytes to an affected application may terminate an unprotected application process, causing a denial of service. The driver's server-monitoring path contains panic recovery and is limited to server-selection failure.
Fix
Microsoft's update · Moderate
- Release Notes — azl3 keda 2.14.1-19 on Azure Linux 3.0 · build 2.14.1-22
- Release Notes — azl3 kubevirt 1.8.4-2 on Azure Linux 3.0 · build 1.8.4-4
- Release Notes — azl3 packer 1.9.5-21 on Azure Linux 3.0 · build 1.9.5-23
- Release Notes — azl3 skopeo 1.14.4-13 on Azure Linux 3.0 · build 1.14.4-14
- Release Notes — azl3 telegraf 1.31.0-33 on Azure Linux 3.0 · build 1.31.0-35
From the 2026-Oct release note of Microsoft's Security Update Guide, revised 2026-10-29.
Patch, vendor advisory and mitigation references on NVD 1
- https://jira.mongodb.org/browse/GODRIVER-4102 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 3
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-27 19:43
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-27 19:43
- First seenCVSS 8.2NVD modified 2026-10-08 20:49
Affected (CPE criteria) 1
cpe:2.3:a:mongodb:go_driver:*:*:*:*:*:mongodb:*:*
References 1
- https://jira.mongodb.org/browse/GODRIVER-4102 Vendor Advisory