Vulnerability in mongodb (CVE-2026-9753)
Summary
Vulnerability in mongodb (CVE-2026-9753). Confidential information can be exposed externally. 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.
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
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-9753 has been found in mongodb.
Confidential information can be exposed externally. CVSS score: 8.1/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-9753" on the vendor's site.
CVE-2026-9753 (mongodb) — CWE-1287 / CVSS v3 8.1
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-1287) exists in mongodb.
Check the vendor advisory for the affected versions of mongodb.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
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-9753 mongodb
References
- web nvd.nist.gov
- web jira.mongodb.org
- web github.com