CVE-2026-66723

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% 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 — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

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

MWDB Core versions >=2.2.0 and <2.19.0 contain a missing authorization vulnerability in the Remote Instances proxy API. The proxy API does not verify authentication for incoming requests, allowing an unauthenticated remote attacker to send arbitrary requests to a remote MWDB instance using the identity and permissions associated with the configured API key. This can result in unauthorized actions being performed on the remote instance as if executed by the user whose API key was used to set up the remote instance. The vulnerability is limited to deployments where Remote Instances have been configured.This issue has been fixed in version 2.19.0

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/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 computed
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
Patch available. Sources: github, github_release.
github_release Patch Available

v2.19.0

Patch available: CERT-Polska/mwdb-core v2.19.0

https://github.com/CERT-Polska/mwdb-core/releases/tag/v2.19.0
github Patch Available

Missing authentication requirement in Remote Instances proxy API · Advisory · CERT-Polska/mwdb-core · GitHub

Affected: 2.19.0.

https://github.com/CERT-Polska/mwdb-core/security/advisories/GHSA-942c-r7qj-w895
generic Patch Available

Vulnerabilities in MWDB Core software | CERT Polska

https://cert.pl/en/posts/2026/07/CVE-2026-66723

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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-08-03 12:37 UTCEG score recompute
  2. 2026-08-03 10:36 UTCEPSS rescore
  3. 2026-08-02 13:39 UTCEG score recompute
  4. 2026-08-02 02:27 UTCEPSS rescore
  5. 2026-08-01 14:42 UTCEG score recompute
  6. 2026-08-01 04:16 UTCEPSS rescore
  7. 2026-07-30 16:45 UTCEG score recompute
  8. 2026-07-30 16:28 UTCEPSS rescore
  9. 2026-07-30 15:42 UTCEG score recompute
  10. 2026-07-29 15:21 UTCEG score recompute
  11. 2026-07-29 14:48 UTCEG score recompute
  12. 2026-07-29 14:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-66723?
CVE-2026-66723 is a high vulnerability published on July 29, 2026. MWDB Core versions >=2.2.0 and <2.19.0 contain a missing authorization vulnerability in the Remote Instances proxy API. The proxy API does not verify authentication for incoming requests, allowing an unauthenticated remote attacker to send arbitrary requests to a remote MWDB instance using the…
When was CVE-2026-66723 disclosed?
CVE-2026-66723 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66723 actively exploited?
CVE-2026-66723 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.3% of all scored CVEs.
What is the CVSS score of CVE-2026-66723?
CVE-2026-66723 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-66723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66723, 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-66723

Explore →

Is Your Infrastructure Affected by CVE-2026-66723?

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

Start Free Scan →Browse All CVEs