CVE-2026-84969

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

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

Score 3.7 from GitHub Security Advisory published 2026-09-03. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
3.7EG
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.3%CVSS: 3.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A memory-handling error in the BSON-to-JSON conversion helpers of the MongoDB C Driver can write a small number of bytes past the end of a heap buffer when a binary field is encoded and the output is cut short at a caller-configured length limit. A party who supplies the document content, with no privileges on the application that links the driver, may cause a small amount of data outside the intended buffer to be altered.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
17
EG Risk 17/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity37% × 45%
Impact severity (EG Severity): CVSS 3.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (3.7): severity, escalated by confirmed exploitation. This CVE's 3.7 is its impact severity (EG Severity), not escalated.

EG Severity
3.7 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

September 3, 2026

Last Modified

September 10, 2026

References (1)

Vendor Advisories for CVE-2026-84969(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
mongo-c-driver1.23.1-1 ... 2.5.2-1 (52 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mongo-c-driver1.30.4-1 ... 2.5.5-1 (23 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mongo-c-driver1.30.4-1 ... 2.5.1-1 (17 versions)
  • every version up to 2.5.2-1: fixed in 2.5.2-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 76 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-18 03:06 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-12 14:53 UTCEG score recompute
  11. 2026-10-11 19:18 UTCEG score recompute
  12. 2026-10-11 16:34 UTCEG score recompute
  13. 2026-10-11 13:52 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-10 04:57 UTCEG score recompute
  17. 2026-10-10 04:57 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-10-07 06:35 UTCEG score recompute
  22. 2026-10-07 06:35 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  25. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
Show 49 more
  1. 2026-10-04 08:19 UTCEG score recompute
  2. 2026-10-04 08:19 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  3. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-01 10:02 UTCEG score recompute
  7. 2026-10-01 10:02 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  8. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-09-28 11:46 UTCEG score recompute
  11. 2026-09-28 11:46 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  12. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-09-25 13:30 UTCEG score recompute
  15. 2026-09-25 13:30 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  16. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-22 15:08 UTCEG score recompute
  20. 2026-09-22 15:08 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  21. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-19 16:52 UTCEG score recompute
  24. 2026-09-19 16:51 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  25. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-16 18:35 UTCEG score recompute
  28. 2026-09-16 18:35 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  29. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-13 18:17 UTCEG score recompute
  33. 2026-09-13 18:17 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  34. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-10 20:01 UTCEG score recompute
  36. 2026-09-10 20:00 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  37. 2026-09-09 14:31 UTCEG score recompute
  38. 2026-09-09 14:31 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  39. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-09-06 16:15 UTCEG score recompute
  41. 2026-09-06 16:15 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  42. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-09-03 17:58 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  45. 2026-09-03 16:33 UTCEG score recompute
  46. 2026-09-03 16:33 UTCGHSA enrichmentGHSA-9xr7-hhfx-wh4c · GitHub CVSS 3.7
  47. 2026-09-03 15:25 UTCEG score recompute
  48. 2026-09-03 15:04 UTCEG score recomputeFirst assessed: 3.7 LOW
  49. 2026-09-03 15:03 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-84969?
CVE-2026-84969 is a low-severity vulnerability; its CVE record was published on September 3, 2026. A memory-handling error in the BSON-to-JSON conversion helpers of the MongoDB C Driver can write a small number of bytes past the end of a heap buffer when a binary field is encoded and the output is cut short at a caller-configured length limit. A party who supplies the document content, with no…
When was the CVE record for CVE-2026-84969 published?
The CVE record for CVE-2026-84969 was published on September 3, 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 September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-84969 actively exploited?
CVE-2026-84969 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84969?
CVE-2026-84969 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-84969?
A fix for CVE-2026-84969 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-84969 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-84969

Explore →

Is Your Infrastructure Affected by CVE-2026-84969?

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

Book a Demo →Browse All CVEs