Deserialization of untrusted data in the command monitoring support of the MongoDB PHP Driver can cause class names…
Summary
Vulnerability reported (CVE-2026-96745). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
Deserialization of untrusted data in the command monitoring support of the MongoDB PHP Driver can cause class names embedded in document content to be honored when the driver builds monitoring event objects. When an application registers a command monitoring subscriber and includes untrusted data in a database operation, an unauthenticated party who controls that data may cause an application class implementing the driver's persistable interface to be instantiated and its unserialization method invoked with the supplied data. The resulting impact depends on the classes available in the application.
Source: NIST National Vulnerability Database NVD
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-96745 has been found.
Risk of unauthorized operations or information disclosure. CVSS score: 5.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2026-96745" on the vendor's site.
CVE-2026-96745 — CWE-502 / CVSS v3 5.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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.
Unsafe deserialization (CWE-502) has been reported.
Check the vendor advisory for the affected versions.
Severity: Medium (CVSS 5.6/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-96745 php-mongodb
- Ubuntu UBUNTU-CVE-2026-96745 pymongo
References
- web cna@mongodb.com
- web cna@mongodb.com
- web cna@mongodb.com
- web cna@mongodb.com
- web cna@mongodb.com