Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-88023 high CVSS 8.3

Vulnerability in mongodb/mongodb (CVE-2026-88023)

Summary

Vulnerability in mongodb/mongodb (CVE-2026-88023). Data can be tampered with by attackers. Mitigation: upgrade to 1.21.5 or later.

Original description

The description as published by the source.

Impact

Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB PHP Library can cause a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable. The affected rename operation may also rename a stored file other than the intended target.

Patches

Fixed in 1.21.5 and 2.4.2.

Workarounds

Validate GridFS IDs.

References

https://jira.mongodb.org/browse/PHPLIB-1929

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-88023 has been found in mongodb/mongodb.
Data can be tampered with by attackers. CVSS score: 8.3/10.
What to do: upgrade mongodb/mongodb to 1.21.5 or later.
If unsure, ask your IT team or search "mongodb/mongodb CVE-2026-88023" on the vendor's site.

CVE-2026-88023 (mongodb/mongodb) — CWE-943 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.21.5 — 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.

❓ What is the problem

A vulnerability (CWE-943) exists in mongodb/mongodb.

📍 Affected scope

Check the vendor advisory for the affected versions of mongodb/mongodb.

🔥 Severity

Severity: High (CVSS 8.3/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.21.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mongodb/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

  1. 1
    Identify exposure identify 
    grep -r 'mongodb/mongodb' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mongodb/mongodb を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade mongodb/mongodb to 1.21.5

    ステージング環境で 1.21.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer mongodb/mongodb
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.2"}]}]
Packagist mongodb/mongodb
[{"type":"ECOSYSTEM","events":[{"introduced":"2.0.0"},{"fixed":"2.4.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details