Security readout for executives and security teams
Plain-English summary
A low-privileged MongoDB user may bypass query-level role restrictions and read or change protected data. The flaw affects specified MongoDB Server versions when API strict mode is not configured. Because exploitation requires an authenticated account, compromised credentials, exposed application accounts, or malicious insiders are the principal business concerns.
Executive priority
Prioritize assessment within days, accelerating for internet-reachable databases, sensitive data, shared application credentials, or insider-risk concerns. Treat confirmed vulnerable non-apiStrict deployments as urgent because successful abuse could expose or alter protected data without disrupting service or requiring victim interaction.
Technical view
Insufficient validation of client-supplied parameters can bypass role-based query-level controls in find, update, delete, and aggregate commands. The CVSS 4.0 score is 8.6: network-accessible, low complexity, low privileges, no user interaction, with high confidentiality and integrity impact but no stated availability impact.
Likely exposure
Potential exposure is limited to the listed MongoDB Server versions—7.0, 8.0, 8.2.0, and 8.3.0—using non-apiStrict configurations and query-level RBAC. The supplied affected-data also states a default status of unaffected, creating scope ambiguity that administrators should resolve through MongoDB guidance.
Exploitation context
The supplied record is not in CISA KEV and cites no evidence of active exploitation. Abuse nevertheless appears practical for an authenticated, low-privileged user because the stated attack has network reachability, low complexity, and requires no user interaction. Public exploit availability is not established by the sources.
Researcher notes
CWE-807 is assigned. Important missing evidence includes precise vulnerable patch ranges, fixed versions, whether apiStrict is a complete mitigation, and exploitation telemetry. The affected-version list and default-unaffected status appear potentially inconsistent; avoid extrapolating broader version ranges until MongoDB clarifies them.
Mitigation direction
- Review MongoDB's advisory ticket for confirmed affected builds, fixed releases, and vendor-approved remediation.
- Evaluate enabling apiStrict where application compatibility and MongoDB guidance permit.
- Restrict network access to MongoDB and remove unnecessary low-privileged accounts.
- Rotate credentials suspected of compromise and review application account permissions.
Validation and detection
- Inventory MongoDB Server versions and identify 7.0, 8.0, 8.2.0, or 8.3.0 deployments.
- Determine whether each relevant deployment uses apiStrict and query-level role controls.
- Review logs for unexpected protected-data reads or writes by low-privileged identities.
- After remediation, verify role restrictions across find, update, delete, and aggregate operations in an authorized test environment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-807: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-13059 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——mongodbCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2mongodbVulnerability scoring details
Base CVSS 4.0 score
8.6HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.mongodb.org/browse/SERVER-128433CVE reference, mongodb
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.