The BSON encoder in the MongoDB PHP Driver converts a string length to a 32-bit value without validation. When an affected application encodes a string near 4 GiB, the allocation size can wrap while the copy operation uses the original length. The resulting heap buffer overflow can corrupt process memory or terminate the PHP process. Reaching this issue requires a non-default runtime configuration that permits multi-gigabyte values. No MongoDB server interaction is required.
CVE-2026-106432
HIGHNVD 8.28.2Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
8.2EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 8.2Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (MongoDB, Inc.) lists MongoDB PHP Driver versions 1.16.0 up to but not including 1.21.11, 2.0.0 up to but not including 2.1.11 and 2.2.0 up to but not including 2.5.4 as affected. No release containing a fix is confirmed on record.
- CVSS v3
- 8.2
- EG Score
- 8.2HIGHmedium confidence
- EG Risk
- 37EG Risk 37/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)Severity82% × 45%The EG Score, 8.2 of 10.Exploitation<0.1% × 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.1%
- EPSS %ILE
- below the 1st
- 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
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 13, 2026
References (1)
- cna@mongodbhttps://jira.mongodb.org/browse/PHPC-2741Vendor Advisory
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-mongodb | 1.15.0+1.11.1+1.9.2+1.7.5-1 ... 2.5.3-1 (12 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-mongodb | 2.0.0-1, 2.0.0-1+deb13u1, 2.1.0-1, 2.5.3-1 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| php-mongodb | 2.0.0-1, 2.1.0-1, 2.5.3-1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× 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-13 20:39 UTCEG score recompute▲ 4.60
- 2026-10-13 20:24 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
- 2026-10-13 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-12 16:39 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:27 UTCEG score recompute
- 2026-10-11 15:00 UTCEG score recompute
- 2026-10-11 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-09 20:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
- 2026-10-08 20:20 UTCEG score recompute
- 2026-10-08 20:03 UTCEG score recompute
- 2026-10-08 19:25 UTCEG score recomputeFirst assessed: 3.6 LOW
- 2026-10-08 19:24 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
6 shownDebian:12:php-mongodb
Frequently asked(5)
What is CVE-2026-106432?
CVE-2026-106432 is a high-severity vulnerability; its CVE record was published on October 8, 2026. The BSON encoder in the MongoDB PHP Driver converts a string length to a 32-bit value without validation. When an affected application encodes a string near 4 GiB, the allocation size can wrap while the copy operation uses the original length. The resulting heap buffer overflow can corrupt process…
When was the CVE record for CVE-2026-106432 published?
The CVE record for CVE-2026-106432 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-106432 actively exploited?
CVE-2026-106432 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-106432?
CVE-2026-106432 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-106432?
No fix for CVE-2026-106432 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 CVE record's CNA (MongoDB, Inc.) lists MongoDB PHP Driver versions 1.16.0 up to but not including 1.21.11, 2.0.0 up to but not including 2.1.11 and 2.2.0 up to but not including 2.5.4 as affected. No release containing a fix is confirmed on record.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-106432
Is Your Infrastructure Affected by CVE-2026-106432?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.