CVE-2026-59509

CRITICALPre-NVD 9.29.2—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this weekElevated
9.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An unauthenticated improper input validation vulnerability in the POST /fetch_cve_data endpoint in cve-search. A remote attacker can manipulate request parameters controlling the MongoDB collection, projected fields, and regular-expression filters to read arbitrary application MongoDB collections. This can expose administrative usernames and password hashes from the mgmt_users collection, enabling offline password cracking and potential administrative account compromise.

CVSS v3
9.2
EG Score
9.2(medium)
EPSS
27.0%
KEV
Not listed

Published

July 5, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 5, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

fix(web): add server-side validations for /fetch_cve_data inputs

Patch available: cve-search/cve-search v6.0.1 (PR #1218 merged 2026-06-22)

https://github.com/cve-search/cve-search/pull/1218
generic

Unauthenticated NoSQL injection in /fetch_cve_data lets any visitor read arbitrary MongoDB collections (admin password hashes) · Issue #1217 · cve-search/cve-search · GitHub

https://github.com/cve-search/cve-search/issues/1217

Vendor Advisories for CVE-2026-59509(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 24× in last 7d / 24× 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.

  1. 2026-07-07 01:25 UTCEG score recompute
  2. 2026-07-07 01:25 UTCGHSA enrichment
  3. 2026-07-06 21:44 UTCEG score recompute
  4. 2026-07-06 21:43 UTCGHSA enrichment
  5. 2026-07-06 18:02 UTCEG score recompute
  6. 2026-07-06 18:01 UTCGHSA enrichment
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 14:19 UTCEG score recompute
  10. 2026-07-06 14:19 UTCGHSA enrichment
  11. 2026-07-06 10:38 UTCEG score recompute
  12. 2026-07-06 10:37 UTCGHSA enrichment
  13. 2026-07-06 06:54 UTCEG score recompute
  14. 2026-07-06 06:54 UTCGHSA enrichment
  15. 2026-07-06 03:13 UTCEG score recompute
  16. 2026-07-06 03:13 UTCGHSA enrichment
  17. 2026-07-05 23:28 UTCEG score recompute
  18. 2026-07-05 23:28 UTCGHSA enrichment
  19. 2026-07-05 19:47 UTCEG score recompute
  20. 2026-07-05 19:47 UTCGHSA enrichment
  21. 2026-07-05 16:06 UTCEG score recompute
  22. 2026-07-05 16:06 UTCGHSA enrichment
  23. 2026-07-05 12:25 UTCEG score recompute
  24. 2026-07-05 12:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59509?
CVE-2026-59509 is a critical vulnerability published on July 5, 2026. An unauthenticated improper input validation vulnerability in the POST /fetchcvedata endpoint in cve-search. A remote attacker can manipulate request parameters controlling the MongoDB collection, projected fields, and regular-expression filters to read arbitrary application MongoDB collections.…
When was CVE-2026-59509 disclosed?
CVE-2026-59509 was first published in the National Vulnerability Database on July 5, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59509 actively exploited?
CVE-2026-59509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59509?
CVE-2026-59509 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2026-59509?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59509, 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-59509

Explore →

Is Your Infrastructure Affected by CVE-2026-59509?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs