{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-116641 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-116641 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-116641 is a high-severity vulnerability in MongoDB Database Tools, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116641 and fix it if it is affected.\n\nWhat it is: CVE-2026-116641 is a high-severity vulnerability in MongoDB Database Tools, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-116641 in the wild and no public exploit code.\n\nAffected product: MongoDB Database Tools. 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-116641/ (Markdown: https://insights.sbomify.com/CVE-2026-116641/index.md)","id":"CVE-2026-116641","markdown":"https://insights.sbomify.com/CVE-2026-116641/index.md","name":"CVE-2026-116641","record":{"aliases":["GHSA-5j5x-575j-vr62"],"analysis":null,"analysis_generated_by":null,"assigner":"mongodb","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"The DB Tools rely on the TLS implementation in Golang’s standard library, which generally uses the system CA store. However, the crypto/x509 package also has its own internal denylist of known-bad CA certificates. Golang 1.27.3 adds the eMudhra certificates to this list.\n\nDB Tools version 100.19.0 was compiled with Golang 1.26.8, which does not include this check.\n\nThe issue is resolved by updating to Golang 1.27.3 in DB Tools 100.20.0","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":"The DB Tools trust certificates issued by recoverable eMudhra intermediate CAs","id":"CVE-2026-116641","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Tanium addressed an improper output sanitization vulnerability in Comply.","id":"CVE-2026-116647"},"packages":[],"prev":{"headline":"Saruf-Ratul HR-Payroll-Management-System chat.php cross site scripting","id":"CVE-2026-116640"},"products":["Database Tools"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["MongoDB"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116641/"}