Unauthenticated service interruption via unhandled logging errors
Published Aug 28, 2026 · Updated Aug 28, 2026
Improper error handling in MongoDB Connector for BI before 2.14.31 allows remote attackers to interrupt SQL service via log exhaustion. The mongosqld logging path fails to handle errors from log writes or rotation after connection activity fills its backing storage, terminating the shared process. Network access to the listener is sufficient; all connected SQL clients lose service, and startup continues to fail while the log storage remains full.
Summary
What happened
Improper error handling in MongoDB Connector for BI before 2.14.31 allows remote attackers to interrupt SQL service via log exhaustion. The mongosqld logging path fails to handle errors from log writes or rotation after connection activity fills its backing storage, terminating the shared process. Network access to the listener is sufficient; all connected SQL clients lose service, and startup continues to fail while the log storage remains full.
The record
- CVE
- CVE-2026-81517
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- MongoDB
- Product
- MongoDB Connector for BI
- Classifications
- CWE-248, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=0 <2.14.31
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.
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