Threadlinqs IntelligenceStart free

Vendor4 products tracked

MongoDB vulnerabilities & exploitation

1 in CISA KEV4 with public exploit

As of 2026-11-19, Threadlinqs tracks 8 MongoDB CVEs, 1 in the CISA Known Exploited Vulnerabilities catalog, linked to 11 tracked threat campaigns and 1 named threat actor.

CVEs
8Since 2025
CISA KEV
113% of CVEs
Critical
1CVSS v3 9.0+
Avg CVSS
6.8/10Max 9
Threats
11Linked campaigns
Actors
1Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 8 MongoDB CVEs published between and . The busiest month was 2026-08 (5 new CVEs). 1 of them (13%) are listed in CISA KEV, which means exploitation in the wild has been confirmed.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 8 of 8 tracked MongoDB CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 8 CVEs; 4 distinct MongoDB products are affected. The most frequently affected:

  • C# Driver 4 CVEs
  • Server 2 CVEs
  • Atlas SQL JDBC Driver 1 CVE
  • Rust Driver 1 CVE

Threat activity

11 tracked threat campaigns reference MongoDB products or exploit MongoDB CVEs:

Threat actors targeting MongoDB

Named threat actors attributed to campaigns that involve MongoDB products or CVEs, with the number of linked campaigns:

How to prioritise MongoDB patching

This order follows the data Threadlinqs holds for MongoDB, not a generic severity checklist:

  • 1 of 8 MongoDB CVEs (13%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2025-14847.
  • Outside KEV, the highest EPSS scores are CVE-2026-118383 (0.7%), CVE-2026-81526 (0.2%), CVE-2026-81527 (0.2%).
  • 1 CVE scores Critical and 3 High on CVSS v3 (maximum 9, average 6.8); sequence these after KEV and high-EPSS items.
  • 4 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-11-19 and refresh daily.