Missing Authorization in MongoDB Sharded Transaction Commit/Abort Handling Leads to Cross-Shard Data Inconsistency (CVE-2026-18709) | HOL Guard CVE

Medium · CVSS 6.4CVE-2026-18709

Missing Authorization in MongoDB Sharded Transaction Commit/Abort Handling Leads to Cross-Shard Data Inconsistency

Answer in brief

CVE-2026-18709 records a Medium severity (CVSS 6.4) vulnerability in Missing Authorization in MongoDB Sharded Transaction Commit/Abort Handling Leads to Cross-Shard Data Inconsistency. The current sources do not mark it as known exploited. The current feed maps MongoDB/MongoDB Server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 11, 2026Updated Sep 16, 2026Source checked Sep 25, 2026First seen by HOL Aug 11, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.4
Exploitation: Not marked as known exploited
Affected software: 5 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 6.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps MongoDB/MongoDB Server (generic). Check affected ranges and fixed versions before updating.

Affected products and reported versions
Product	Affected versions	Fixed versions
cpe:2.3:a:mongodb:mongodb::::::::	Not reported	Not reported
cpe:2.3:a:mongodb:mongodb:9.0.0:alpha0:::-:-::	Not reported	Not reported
cpe:2.3:a:mongodb:mongodb:9.0.0:alpha1:::-:-::	Not reported	Not reported
cpe:2.3:a:mongodb:mongodb:9.1.0:alpha0:::-:-::	Not reported	Not reported

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
MongoDB/MongoDB Servergeneric	>=8.3.0 <8.3.8 \|\| >=8.0 <8.0.29 \|\| >=7.0 <7.0.40	8.3.8, 8.0.29, 7.0.40

Recommended response

Check inventory. Check lockfiles and deployed manifests for MongoDB/MongoDB Server.
Review the reported fix. Update MongoDB/MongoDB Server to 8.3.8 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 11, 2026

Sources and claim methodology

Source referencejira.mongodb.org

Upstream source description

An issue in MongoDB Server could allow an authenticated user with direct network access to a shard to improperly commit or abort an in-progress prepared transaction, bypassing the intended transaction coordination process. This could result in cross-shard data inconsistency, cluster clock corruption, and violation of transaction atomicity guarantees.

Quoted source text, attributed separately from HOL analysis.