CVE-2026-25612Network attack vector

Authenticated collection access interruption via ResourceId collisions

Published Feb 10, 2026 · Updated Feb 10, 2026

Resource ID collision in MongoDB Server allows remote authenticated users to interrupt access to unrelated collections through conflicting locks. The lock manager encodes collection resources as ResourceId values without guaranteeing uniqueness, so distinct collections can resolve to the same lock. Database access is required; affected releases are 7.0 before 7.0.29, 8.0 before 8.0.18, and 8.2 before 8.2.4, and the collision blocks operations rather than reading or altering data.

CVSS severity7.1
High
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource ID collision in MongoDB Server allows remote authenticated users to interrupt access to unrelated collections through conflicting locks. The lock manager encodes collection resources as ResourceId values without guaranteeing uniqueness, so distinct collections can resolve to the same lock. Database access is required; affected releases are 7.0 before 7.0.29, 8.0 before 8.0.18, and 8.2 before 8.2.4, and the collision blocks operations rather than reading or altering data.

The record

CVE
CVE-2026-25612
Published
Feb 10, 2026
Updated
Feb 10, 2026
Vendor
MongoDB
Product
MongoDB Server
Classifications
CWE-412, CAPEC-25, T1499.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Feb 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=7.0 <7.0.29
  2. Affected versionversion=8.0 <8.0.18
  3. Affected versionversion=8.2 <8.2.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

MongoDB · MongoDB Serverversion=7.0 <7.0.29; version=8.0 <8.0.18; version=8.2 <8.2.4

Published CVSS scores

7.1MongoDB, Inc.CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
6.5MongoDB, Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-412Unrestricted Externally Accessible Lock
CAPEC-25Forced Deadlock
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo