{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-81490 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81490 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81490 is a high-severity denial of service vulnerability in MongoDB BI Connector, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81490 and fix it if it is affected.\n\nWhat it is: CVE-2026-81490 is a high-severity denial of service vulnerability in MongoDB BI Connector, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81490 in the wild and no public exploit code.\n\nAffected product: MongoDB BI Connector. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-81490/ (Markdown: https://insights.sbomify.com/CVE-2026-81490/index.md)","id":"CVE-2026-81490","markdown":"https://insights.sbomify.com/CVE-2026-81490/index.md","name":"CVE-2026-81490","record":{"aliases":["GHSA-g954-97w2-99wv"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MongoDB BI Connector","requires_auth":"low_privilege","summary":"A malicious database user can cause the MongoDB BI Connector to stop serving SQL queries by creating a view that fails during schema sampling.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"bi_connector","vendor":"mongodb"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"A database user able to create a view in a namespace that MongoDB Connector for BI samples can cause the schema-sampling routine to stop functioning by defining a view whose evaluation reliably fails. The sampling logic classifies the resulting server message as transient and, after the configured retries are exhausted, proceeds without a valid result, ending the schema refresh routine. The mongosqld process continues running without a usable schema, so SQL clients are unable to obtain results until an operator removes the view or excludes its namespace from sampling.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"MongoDB Connector for BI Improper Error Handling During Schema Sampling May Cause Loss of SQL Service","id":"CVE-2026-81490","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"boxpositron with-context-mcp index.ts project_folder path traversal","id":"CVE-2026-81491"},"packages":[],"prev":{"headline":"bsmi021 mcp-file-context-server Path Resolution index.ts read_context path traversal","id":"CVE-2026-81486"},"products":["BI Connector"],"published":"2026-08-28","related":[{"cvss_score":8.7,"headline":"MongoDB Connector for BI Improper Error Handling of Log Write Failures May Cause Loss of SQL Service","id":"CVE-2026-81517","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.7,"headline":"BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections","id":"CVE-2026-81518","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.7,"headline":"MongoDB Connector for BI Unbounded Authentication Negotiation Leading to Connection Exhaustion","id":"CVE-2026-81520","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.5,"headline":"MongoDB Connector for BI Unescaped Object Names in Generated SHOW CREATE Output","id":"CVE-2026-77586","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.2,"headline":"MongoDB BI Connector Improper Memory Handling During Failed Kerberos Authentication May Cause Process Termination","id":"CVE-2026-75159","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":5.6,"headline":"MongoDB Connector for BI Incomplete Escaping of Stored Metadata in Generated SHOW CREATE Output","id":"CVE-2026-77184","kev_date_added":null,"published":"2026-08-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["MongoDB"]},"summary":"A malicious database user can cause the MongoDB BI Connector to stop serving SQL queries by creating a view that fails during schema sampling.","url":"https://insights.sbomify.com/CVE-2026-81490/"}