CVE-2025-6707 json
Race condition in privilege cache invalidation cycle
published last yr. modified last mo. also BIT-mongodb-2025-6707 , EUVD-2025-19227
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
Under certain conditions, an authenticated user request may execute with stale privileges following an intentional change by an authorized administrator. This issue affects MongoDB Server v5.0 version prior to 5.0.31, MongoDB Server v6.0 version prior to 6.0.24, MongoDB Server v7.0 version prior to 7.0.21 and MongoDB Server v8.0 version prior to 8.0.5.
Patch / fix
- bitnami mongodb 5.0.31, 6.0.24, 7.0.21, 8.0.5
- MongoDB Inc MongoDB Server 5.0.31, 6.0.24, 7.0.21, 8.0.5
Is CVE-2025-6707 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| OSV | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=5.0.0, <5.0.31 >=6.0.0, <6.0.24 >=7.0.0, <7.0.21 >=8.0.0, <8.0.5 |
5.0.31 6.0.24 7.0.21 8.0.5 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-93497
issue-tracking, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-6707
web
Sources
- CVE List CVE-2025-6707
- NVD CVE-2025-6707
- OSV BIT-mongodb-2025-6707
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.