NVD / CVE Program· CNA mongodb

CVE-2026-88032: Application denial of service via cancellation race in reactive client-side encryption in MongoDB Java Driver

Noroxi assessment

Priority: Monitor (action score 32/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: MongoDB Java Driver 5.11.1; MongoDB org.mongodb:mongodb-crypt Maven package 5.11.1; MongoDB org.mongodb:mongodb-driver-reactivestreams Maven package 5.11.1.

Low priority for now. Upgrade to MongoDB Java Driver 5.11.1; MongoDB org.mongodb:mongodb-crypt Maven package 5.11.1; MongoDB org.mongodb:mongodb-driver-reactivestreams Maven package 5.11.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A use-after-free in the reactive client-side encryption component of the MongoDB Java Driver can cause native resources to be freed while an affected encrypted operation is still using them when the operation is cancelled. A party able to cause such an operation to be cancelled may cause the hosting application process to terminate. Reaching the issue requires an affected reactive encryption configuration that retrieves KMS credentials on demand.

HighCVSS 8.2 · v4.0—No exploit Fix available

EUVD-2026-75668

Published: Sep 10, 2026
Updated: Sep 16, 2026
EPSS: 0.2% · 17th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · mongodb: 8.2; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
mongodb	java driver	cpe:2.3:a:mongodb:java_driver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

mongodb java driver4.2.0 and later · before 5.11.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mongodb). Independent of NVD's CPE analysis and usually ahead of it.

MongoDB Java Driver
- 4.2.0 and later · before 5.11.1affected · semver
MongoDB org.mongodb:mongodb-crypt Maven package
- 1.4.0 and later · before 5.11.1affected · semver
MongoDB org.mongodb:mongodb-driver-reactivestreams Maven package
- 4.6.0 and later · before 5.11.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	mongo-java-driver	from 0	—

Same product

mongodb: all records

Other highest-scoring records for the same primary product.

CVE-2026-18710Cleartext Storage of Sensitive Information in MongoDB Driver Logging During Client Initialization
32Monitor
CVE-2026-118581NoSQL injection via mismatched BSON size prefix in raw document splice to the wire protocol
27Monitor
CVE-2021-20328MongoDB Java driver client-side field level encryption not verifying KMS host name
27Monitor

Published before and after this one in the same product

Later →CVE-2026-88033Sep 10, 2026 · GridFS data disclosure and deletion via query-operator injection in file IDs in the MongoDB Java Driver
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
MongoDB Java Driver	5.11.1	Vendor (CNA)
MongoDB org.mongodb:mongodb-crypt Maven package	5.11.1	Vendor (CNA)
MongoDB org.mongodb:mongodb-driver-reactivestreams Maven package	5.11.1	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

MongoDBHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

jira.mongodb.org/browse/JAVA-6276

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records