PatchSiren cyber security CVE debrief
CVE-2026-76798 MongoDB CVE debrief
The MongoSQL Transition Readiness Tool is vulnerable to a report generation issue. A user able to issue queries through the BI Connector can influence log content so that markup supplied in a query is interpreted by the browser when an operator later generates and opens the report. This may disclose other users' logged query text and user names to an external party or present misleading content to the operator.
- Vendor
- MongoDB
- Product
- BI Connector Transition Readiness Report
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-28
- Original CVE updated
- 2026-09-17
- Advisory published
- 2026-08-28
- Advisory updated
- 2026-09-17
Who should care
Defenders and operators who use the MongoSQL Transition Readiness Tool and BI Connector should be aware of this vulnerability and take steps to verify and mitigate it, especially in environments where multiple users access the BI Connector and generate reports.
Why it matters
The MongoSQL Transition Readiness Tool is vulnerable to a report generation issue that may disclose sensitive information or present misleading content. Defenders should prioritize verifying and mitigating this vulnerability, especially in environments where multiple users access the BI Connector and generate reports.
- Potential disclosure of sensitive query text and user names to external parties
- Possible presentation of misleading content to operators
- Need for verification of affected versions and remediation steps
- Importance of input validation and output encoding for query text and user names
Technical summary
The MongoSQL Transition Readiness Tool writes query text and user names read from BI Connector log files into its generated HTML report without encoding them for that output context. A user able to issue queries through the BI Connector can influence log content so that markup supplied in a query is interpreted by the browser when an operator later generates and opens the report, potentially disclosing other users' logged query text and user names or presenting misleading content. This issue requires verification of affected versions and remediation steps, especially in environments where multiple users access the BI Connector and generate reports.
Defensive priority
Defenders should prioritize verifying and mitigating this vulnerability, especially in environments where multiple users access the BI Connector and generate reports.
Recommended defensive actions
- Verify the version of MongoSQL Transition Readiness Tool and check if it is vulnerable
- Restrict access to the BI Connector to trusted users
- Implement input validation and output encoding for query text and user names
- Monitor logs for suspicious query activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description and potential impact. However, additional information on affected versions and remediation steps is limited.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-76798 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-76798
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-76798 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-76798
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.mongodb.com/docs/sql-interface/changelog/
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.