The MongoSQL Transition Readiness Tool writes database and collection names into its generated CSV reports without neutralizing leading characters that spreadsheet applications treat as formulas. A user with write privileges on the cluster can choose a namespace name that is later evaluated as a formula when an operator opens the generated report in a spreadsheet application, which may result in unintended disclosure of report contents or execution of external content on the operator's workstation. Generating a report for the affected namespace and opening it in a spreadsheet application is required.
CVE-2026-76797
Score 6.3 from GitHub Security Advisory published 2026-08-28. a secondary CVSS source baseline 6.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity63% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026SQL Interface Changelog - SQL Interface - MongoDB Docs
https://www.mongodb.com/docs/sql-interface/changelog/Vendor Advisories for CVE-2026-76797(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:53 UTCEG score recompute
- 2026-08-29 21:53 UTCGHSA enrichment
- 2026-08-28 20:24 UTCEG score recompute
- 2026-08-28 19:37 UTCEG score recompute
- 2026-08-28 19:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-1236
- CVE-2020-36962EG 9.8EPSS p96CRITICAL
- CVE-2020-36941EG 9.8CRITICAL
- CVE-2020-10131EG 9.8CRITICAL
- CVE-2020-22274EG 9.8CRITICAL
- CVE-2020-22276EG 9.8CRITICAL
- CVE-2020-11548EG 9.8EPSS p92CRITICAL
- CVE-2020-7947EG 9.8CRITICAL
- CVE-2020-9347EG 9.8EPSS p94CRITICAL
- CVE-2019-0403EG 9.8CRITICAL
- CVE-2019-4521EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-76797?
When was CVE-2026-76797 disclosed?
Is CVE-2026-76797 actively exploited?
What is the CVSS score of CVE-2026-76797?
How do I remediate CVE-2026-76797?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76797
Is Your Infrastructure Affected by CVE-2026-76797?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.