A vulnerability was determined in kofrasa mingo up to 7.2.1. This impacts the function update/updateOne/updateMany of the component Update API. Executing a manipulation of the argument Set can lead to improperly controlled modification of object prototype attributes. The attack may be launched remotely. Upgrading to version 7.2.2 will fix this issue. This patch is called fadc398251792c2ba441cbc539f359fc7943c0c2. It is recommended to upgrade the affected component.
CVE-2026-15698
MEDIUMPre-NVD 6.36.3—Trending — 5 sources updated this week
EchelonGraph scoreHIGH confidence
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-14. a secondary CVSS source baseline 6.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(high)
- EPSS
- 17.7%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (3)
Auto-updated Jul 14, 2026🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
GitHub - kofrasa/mingo: MongoDB query language for in-memory objects · GitHub
https://github.com/kofrasa/mingo/github_commit
commit fadc39825179 (kofrasa/mingo)
Fix landed in kofrasa/mingo commit fadc39825179 — awaiting tagged release
https://github.com/kofrasa/mingo/commit/fadc398251792c2ba441cbc539f359fc7943c0c2generic🟡 PoC Available
Prototype pollution in `mingo/updater` via `$set` path segments · Issue #606 · kofrasa/mingo · GitHub
https://github.com/kofrasa/mingo/issues/606Vendor Advisories for CVE-2026-15698(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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-15 16:57 UTCEPSS rescore
- 2026-07-15 14:31 UTCEG score recompute
- 2026-07-15 14:31 UTCGHSA enrichment
- 2026-07-14 17:20 UTCNVD updateCVSS v4 → 2.1
- 2026-07-14 15:41 UTCEG score recompute
- 2026-07-14 15:40 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(5)
What is CVE-2026-15698?
CVE-2026-15698 is a medium vulnerability published on July 14, 2026. A vulnerability was determined in kofrasa mingo up to 7.2.1. This impacts the function update/updateOne/updateMany of the component Update API. Executing a manipulation of the argument Set can lead to improperly controlled modification of object prototype attributes. The attack may be launched…
When was CVE-2026-15698 disclosed?
CVE-2026-15698 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15698 actively exploited?
CVE-2026-15698 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-15698?
CVE-2026-15698 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-15698?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15698, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15698
Is Your Infrastructure Affected by CVE-2026-15698?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.