An unauthenticated remote client can cause excessive CPU consumption on a MongoDB server by sending a specific combination of parameters to the awaitable hello command in exhaust mode. The server's handling of this combination results in a response loop that bypasses normal throttling, allowing a small number of connections to degrade server availability.
CVE-2026-13074
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 35.9%
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 23, 2026
Advisory Details (1)
Auto-updated Jul 22, 2026Vendor Advisories for CVE-2026-13074(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 21:03 UTCEG score recompute
- 2026-07-22 20:05 UTCEG score recompute
- 2026-07-22 20:00 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-770
- CVE-2018-20033EG 9.8CRITICAL
- CVE-2019-11479NVD 7.5EG 9.0EPSS 100%HIGH
- CVE-2019-11478NVD 5.3EG 9.0EPSS 100%MEDIUM
- CVE-2019-10088EG 8.8EPSS 91%HIGH
- CVE-2018-15462EG 8.6HIGH
- CVE-2018-15460EG 8.6HIGH
- CVE-2018-0137EG 8.6HIGH
- CVE-2008-5180NVD 5.3EG 7.9EPSS 99%MEDIUM
- CVE-2019-10094EG 7.8HIGH
- CVE-2018-16865EG 7.8HIGH
Frequently asked(5)
What is CVE-2026-13074?
When was CVE-2026-13074 disclosed?
Is CVE-2026-13074 actively exploited?
What is the CVSS score of CVE-2026-13074?
How do I remediate CVE-2026-13074?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13074
Is Your Infrastructure Affected by CVE-2026-13074?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.