CVE-2026-96749

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

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

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-10-05. A secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-86348 (ENISA EUVD) · GHSA-v4x9-3549-crwv (GitHub Security Advisories) · PYSEC-2026-4296 (OSV.dev)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An integer overflow in the BSON document encoding component of the MongoDB Python Driver's bundled native extension may occur when a single document is built from an unusually large amount of caller-supplied data. Size arithmetic is performed in a signed 32-bit type, and the guard meant to catch the overflow is written in a form whose behavior is not defined by the C language standard. A party with no privileges who can place a very large value into data that an application encodes may, depending on how the native extension was built, cause a write outside the bounds of an allocated buffer inside the application's own process.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
8th
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 (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 24, 2026

Last Modified

September 26, 2026

Advisory Details (1)

Auto-updated Sep 24, 2026
Patch available.
Web page

mongo-python-driver/doc/changelog.rst at 4.18.2 · mongodb/mongo-python-driver · GitHub

https://github.com/mongodb/mongo-python-driver/blob/4.18.2/doc/changelog.rst

Vendor Advisories for CVE-2026-96749(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17918163162026-10-21redhat
redhatrhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9:17918672082026-10-21redhat
pippymongo @ 4.18.2 (fixes < 4.18.2)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pymongo3.11.0-1 ... 4.7.3-2 (19 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pymongo4.10.1-6 ... 4.18.2-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pymongo4.10.1-6 ... 4.18.1-1 (9 versions)
  • every version up to 4.18.2-1: fixed in 4.18.2-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pymongo0.1.1pre ... 4.9.2 (172 versions)
  • every version up to 4.18.2: fixed in 4.18.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. 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. 1 repeat row among the latest 89 is merged into the row it repeats.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-11 14:29 UTCEchelonGraph re-scored
  4. 2026-11-11 14:29 UTCVendor advisory
  5. 2026-11-11 14:29 UTCGHSA enrichmentGHSA-v4x9-3549-crwv · GitHub severity HIGH · GitHub CVSS 8.4
  6. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-11-04 23:49 UTCEchelonGraph re-scored
  13. 2026-11-04 23:49 UTCVendor advisory
  14. 2026-11-04 23:49 UTCGHSA enrichmentGHSA-v4x9-3549-crwv · GitHub severity HIGH · GitHub CVSS 8.4
  15. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-11-03 08:38 UTCEchelonGraph re-scored
  18. 2026-11-03 08:38 UTCVendor advisory
  19. 2026-11-03 08:38 UTCGHSA enrichmentGHSA-v4x9-3549-crwv · GitHub severity HIGH · GitHub CVSS 8.4
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-v4x9-3549-crwv · GitHub severity HIGH · GitHub CVSS 8.4
  23. 2026-11-01 07:37 UTCEchelonGraph re-scored
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 63 more
  1. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-27 17:56 UTCEchelonGraph re-scored
  4. 2026-10-27 17:56 UTCVendor advisory
  5. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-25 13:48 UTCEchelonGraph re-scored
  9. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-19 18:55 UTCEchelonGraph re-scored
  15. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-18 02:57 UTCEchelonGraph re-scored
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-13 04:06 UTCEchelonGraph re-scored
  24. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-12 14:40 UTCEchelonGraph re-scored
  26. 2026-10-11 19:11 UTCEchelonGraph re-scored
  27. 2026-10-11 16:27 UTCEchelonGraph re-scored
  28. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-10-11 13:39 UTCEchelonGraph re-scored
  30. 2026-10-11 07:03 UTCEchelonGraph re-scored
  31. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-10-10 06:15 UTCEchelonGraph re-scored
  33. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-10-09 05:25 UTCEchelonGraph re-scored
  35. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-10-08 02:00 UTCEchelonGraph re-scored
  37. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-10-07 01:00 UTCEchelonGraph re-scored
  39. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-10-06 00:11 UTCEchelonGraph re-scored
  41. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-10-03 22:34 UTCEchelonGraph re-scored
  43. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-10-02 21:45 UTCEchelonGraph re-scored
  45. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-10-01 20:56 UTCEchelonGraph re-scored
  47. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-09-30 20:05 UTCEchelonGraph re-scored
  49. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  50. 2026-09-29 19:14 UTCEchelonGraph re-scored
  51. 2026-09-29 06:49 UTCEchelonGraph re-scored
  52. 2026-09-28 18:25 UTCEchelonGraph re-scored
  53. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-09-27 17:36 UTCEchelonGraph re-scored
  55. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-09-26 16:48 UTCEchelonGraph re-scored
  57. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  58. 2026-09-26 04:22 UTCEchelonGraph re-scored
  59. 2026-09-26 04:06 UTCEchelonGraph re-scored
  60. 2026-09-24 20:20 UTCEchelonGraph re-scored
  61. 2026-09-24 19:22 UTCEchelonGraph re-scored
  62. 2026-09-24 18:27 UTCEchelonGraph re-scoredFirst assessed: 8.4 HIGH
  63. 2026-09-24 18:26 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-96749?
CVE-2026-96749 is a high-severity vulnerability; its CVE record was published on September 24, 2026. An integer overflow in the BSON document encoding component of the MongoDB Python Driver's bundled native extension may occur when a single document is built from an unusually large amount of caller-supplied data. Size arithmetic is performed in a signed 32-bit type, and the guard meant to catch…
When was the CVE record for CVE-2026-96749 published?
The CVE record for CVE-2026-96749 was published on September 24, 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-96749 actively exploited?
CVE-2026-96749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96749?
CVE-2026-96749 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96749?
A fix for CVE-2026-96749 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-96749 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-96749

Explore →

Is Your Infrastructure Affected by CVE-2026-96749?

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

Book a Demo →Browse All CVEs