CVE-2026-107325

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
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

A fix is available — apply it.

Improper validation of a BSON array length in the MongoDB Go Driver can cause an out-of-bounds index and runtime panic when an application calls bson.RawArray.Validate or bsoncore.Array.Validate on a malformed four-byte array. An unauthenticated actor who can supply raw BSON array data to an affected application may terminate an unprotected application process, causing a denial of service. No confidentiality or integrity impact has been identified.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
27
EG 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.2% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

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

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 8, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Oct 8, 2026
Patch available.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-mongodb-mongo-driver1.12.1+ds1-1 ... 1.8.4+ds1-3 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-mongodb-mongo-driver1.17.1+ds1-2, 1.17.1+ds1-3, 1.17.9+ds1-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-mongodb-mongo-driver1.17.1+ds1-2, 1.17.1+ds1-3, 1.17.9+ds1-1
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 19× 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.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-12 16:38 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-12 01:40 UTCGHSA enrichmentGHSA-frr6-8pf7-f9r2 · GitHub severity HIGH · GitHub CVSS 5.9
  5. 2026-10-11 20:14 UTCEG score recompute
  6. 2026-10-11 18:26 UTCEG score recompute
  7. 2026-10-11 15:00 UTCEG score recompute
  8. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-11 00:07 UTCEG score recompute
  10. 2026-10-11 00:06 UTCGHSA enrichmentGHSA-frr6-8pf7-f9r2 · GitHub severity HIGH · GitHub CVSS 5.9
  11. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-09 22:31 UTCEG score recompute
  13. 2026-10-09 22:31 UTCGHSA enrichmentGHSA-frr6-8pf7-f9r2 · GitHub severity HIGH · GitHub CVSS 5.9
  14. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-08 20:20 UTCEG score recompute
  16. 2026-10-08 19:50 UTCEG score recompute
  17. 2026-10-08 19:18 UTCEG score recompute
  18. 2026-10-08 19:05 UTCEG score recomputeFirst assessed: 5.9 MEDIUM
  19. 2026-10-08 19:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-107325?
CVE-2026-107325 is a medium-severity vulnerability; its CVE record was published on October 8, 2026. Improper validation of a BSON array length in the MongoDB Go Driver can cause an out-of-bounds index and runtime panic when an application calls bson.RawArray.Validate or bsoncore.Array.Validate on a malformed four-byte array. An unauthenticated actor who can supply raw BSON array data to an…
When was the CVE record for CVE-2026-107325 published?
The CVE record for CVE-2026-107325 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-107325 actively exploited?
CVE-2026-107325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107325?
CVE-2026-107325 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-107325?
A fix for CVE-2026-107325 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-107325 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-107325

Explore →

Is Your Infrastructure Affected by CVE-2026-107325?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.