Data access and modification via namespace injection
Published Aug 27, 2026 · Updated Aug 27, 2026
Resource injection in MongoDB C Driver before 2.5.1 allows remote authenticated users to access or modify unintended data resources. libmongoc composes database and collection namespaces without rejecting periods in database names or NUL bytes in either name, so encoding can silently retarget an operation. Exploitation requires an application to place untrusted input into those name components; consequences are limited to data reachable through the application's MongoDB privileges.
Summary
What happened
Resource injection in MongoDB C Driver before 2.5.1 allows remote authenticated users to access or modify unintended data resources. libmongoc composes database and collection namespaces without rejecting periods in database names or NUL bytes in either name, so encoding can silently retarget an operation. Exploitation requires an application to place untrusted input into those name components; consequences are limited to data reachable through the application's MongoDB privileges.
The record
- CVE
- CVE-2026-81524
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- MongoDB
- Product
- MongoDB .NET/C# Driver
- Classifications
- CWE-99, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <2.5.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo