Skip to content
Applications

CVE-2026-81490

8.3
High
EPSS 0.24%Patch availableSep 1, 2026

MongoDB BI Connector schema-sampling can be broken by crafted view, halting SQL query results.

common questions

Is CVE-2026-81490 being exploited?

Not confirmed. CVE-2026-81490 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-81490?

CVE-2026-81490 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-81490?

Yes. A fix has been recorded for CVE-2026-81490. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-81490 affect?

CVE-2026-81490 affects MongoDB Connector for BI (mongosqld), MongoDB deployments using BI Connector, Namespaces/views sampled by mongosqld. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-81490?

Apply MongoDB BI Connector patch, remove or exclude the malicious view, and restrict createView privileges.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MongoDB Connector for BI (mongosqld)MongoDB deployments using BI ConnectorNamespaces/views sampled by mongosqld
impact

A database user who can create a view can stop schema sampling, causing mongosqld to lack a usable schema and deny SQL query results until remediation.

action required

Immediate action required

affected versions
MongoDB BI Connector
  • affected< 2.14.31

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free