An integer overflow in BSON value-length handling in the MongoDB Go Driver can cause a runtime panic when an application validates or accesses a malformed BSON document. An unauthenticated actor who can supply BSON bytes to an affected application may terminate an unprotected application process, causing a denial of service. The driver's server-monitoring path contains panic recovery and is limited to server-selection failure.
CVE-2026-107324
MEDIUMPre-NVD 5.95.9—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-10-08. A secondary CVSS source baseline 5.9; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.9Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 5.9
- EG Score
- 5.9MEDIUMhigh confidence
- EG Risk
- 27EG Risk 27/100
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 computed (value × EchelonGraph’s weight)Severity59% × 45%The EG Score, 5.9 of 10.Exploitation0% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 12th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
Published
October 8, 2026
Last Modified
October 8, 2026
Advisory Details (1)
Auto-updated Oct 8, 2026No fix on record yet.
Vendor Advisories for CVE-2026-107324(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 11× in last 7d / 11× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-10 22:54 UTCEG score recompute
- 2026-10-10 22:54 UTCGHSA enrichmentGHSA-hrj7-rwg8-vqvg · GitHub severity HIGH · GitHub CVSS 5.9
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-09 21:55 UTCEG score recompute
- 2026-10-09 21:55 UTCGHSA enrichmentGHSA-hrj7-rwg8-vqvg · GitHub severity HIGH · GitHub CVSS 5.9
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-08 20:20 UTCEG score recompute
- 2026-10-08 19:35 UTCEG score recompute
- 2026-10-08 19:18 UTCEG score recompute
- 2026-10-08 19:05 UTCEG score recompute
- 2026-10-08 19:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-107324?
CVE-2026-107324 is a medium vulnerability published on October 8, 2026. An integer overflow in BSON value-length handling in the MongoDB Go Driver can cause a runtime panic when an application validates or accesses a malformed BSON document. An unauthenticated actor who can supply BSON bytes to an affected application may terminate an unprotected application process,…
When was the CVE record for CVE-2026-107324 published?
The CVE record for CVE-2026-107324 was published on October 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-107324 actively exploited?
CVE-2026-107324 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107324?
CVE-2026-107324 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107324?
No fix for CVE-2026-107324 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-107324 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-107324
Is Your Infrastructure Affected by CVE-2026-107324?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.