Out-of-Bounds Write in mongodb (CVE-2026-8053)
Summary
Out-of-bounds write in mongodb (CVE-2026-8053). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2 or later.
Original description
The description as published by the source.
An issue in MongoDB Server's time-series collection implementation allows an authenticated user with database write privileges to trigger an out-of-bounds memory write in the mongod process. The issue results from an inconsistency in the internal field-name-to-index mapping within the time-series bucket catalog. Under certain conditions this can result in arbitrary code execution.
This issue impacts MongoDB Server v5.0 versions prior to 5.0.33, v6.0 versions prior to 6.0.28, v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.
Source: NIST National Vulnerability Database 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-8053 has been found in mongodb.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade mongodb to 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2 or later.
If unsure, ask your IT team or search "mongodb CVE-2026-8053" on the vendor's site.
CVE-2026-8053 (mongodb) — CWE-787 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2 — 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.
Out-of-bounds write (CWE-787) exists in mongodb.
Check the vendor advisory for the affected versions of mongodb.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2.
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 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2ステージング環境で 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-8053 mongodb
References
- web jira.mongodb.org
- web nvd.nist.gov
- web github.com