CVE-2026-107325: Application denial of service via missing BSON array length validation in MongoDB Go Driver
Application denial of service via missing BSON array length validation in MongoDB Go Driver
Other sources
Improper validation of a BSON array length in the MongoDB Go Driver can cause an out-of-bounds index and runtime panic when an application calls bson.RawArray.Validate or bsoncore.Array.Validate on a malformed four-byte array. An unauthenticated actor who can supply raw BSON array data to an affected application may terminate an unprotected application process, causing a denial of service. No confidentiality or integrity impact has been identified.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
azurelinux/skopeoto a version that resolves this vulnerability.Fixed in 1.14.4-14 - Upgrade
Upgrade
azurelinux/kubevirtto a version that resolves this vulnerability.Fixed in 1.8.4-4 - Upgrade
Upgrade
azurelinux/kedato a version that resolves this vulnerability.Fixed in 2.14.1-22 - Upgrade
Upgrade
azurelinux/packerto a version that resolves this vulnerability.Fixed in 1.9.5-23 - Upgrade
Upgrade
azurelinux/telegrafto a version that resolves this vulnerability.Fixed in 1.31.0-35 - Upgrade
Upgrade
azurelinux/kata-containers-ccto a version that resolves this vulnerability.Fixed in 3.15.0.aks0-23 - Upgrade
Upgrade
azurelinux/kata-containersto a version that resolves this vulnerability.Fixed in 4.1.0.kata1-2
Event History
Frequently Asked Questions
Which applications are exposed to this denial-of-service condition?
Applications using the MongoDB Go Driver are exposed if they call bson.RawArray.Validate or bsoncore.Array.Validate on attacker-controlled raw BSON array data. The affected input is a malformed four-byte BSON array.
Does an attacker need authentication or user interaction to trigger the issue?
No. An unauthenticated actor can trigger the condition if they can supply raw BSON array data to the affected application; no user interaction is required.
What is the operational impact of successful exploitation?
The malformed array can cause an out-of-bounds index and runtime panic, terminating an unprotected application process. The reported impact is availability only; no confidentiality or integrity impact has been identified.