Vulnerability in mongodb (CVE-2026-9752)
Summary
Vulnerability in mongodb (CVE-2026-9752). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 7.0.35, 8.0.24, 8.2.10, 8.3.3 or later.
Original description
The description as published by the source.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS.
Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9752 has been found in mongodb.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade mongodb to 7.0.35, 8.0.24, 8.2.10, 8.3.3 or later.
If unsure, ask your IT team or search "mongodb CVE-2026-9752" on the vendor's site.
CVE-2026-9752 (mongodb) — CWE-476 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 7.0.35, 8.0.24, 8.2.10, 8.3.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-476) exists in mongodb.
Check the vendor advisory for the affected versions of mongodb.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 7.0.35, 8.0.24, 8.2.10, 8.3.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mongodb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mongodb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mongodbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mongodb to 7.0.35, 8.0.24, 8.2.10, 8.3.3ステージング環境で 7.0.35, 8.0.24, 8.2.10, 8.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-9752 mongodb
References
- advisory jira.mongodb.org
- web nvd.nist.gov
- web github.com