A vulnerability allowing a low-privileged user to retrieve report data outside the scope of a shared report link.
CVE-2026-64630
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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).
- 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(medium)
- EG Risk
- 24(Track)EG Risk 24/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%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
August 4, 2026
Last Modified
August 4, 2026
Advisory Details (1)
Auto-updated Aug 4, 2026Vendor Advisories for CVE-2026-64630(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 19× in last 7d / 44× 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-08-20 04:01 UTCEG score recompute
- 2026-08-20 04:01 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 03:22 UTCEG score recompute
- 2026-08-19 03:22 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 02:43 UTCEG score recompute
- 2026-08-18 02:42 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 02:04 UTCEG score recompute
- 2026-08-17 02:04 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 01:26 UTCEG score recompute
- 2026-08-16 01:26 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 00:47 UTCGHSA enrichment
- 2026-08-14 00:09 UTCEG score recompute
- 2026-08-14 00:09 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:30 UTCEG score recompute
- 2026-08-12 23:30 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 22:52 UTCEG score recompute
- 2026-08-11 22:52 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
Show 19 moreShow fewer
- 2026-08-10 22:14 UTCGHSA enrichment
- 2026-08-09 21:36 UTCEG score recompute
- 2026-08-09 21:36 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-08 20:58 UTCEG score recompute
- 2026-08-08 20:58 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:19 UTCEG score recompute
- 2026-08-07 20:19 UTCGHSA enrichment
- 2026-08-06 19:41 UTCEG score recompute
- 2026-08-06 19:41 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:03 UTCGHSA enrichment
- 2026-08-04 18:25 UTCEG score recompute
- 2026-08-04 17:23 UTCEG score recompute
- 2026-08-04 16:27 UTCEG score recompute
- 2026-08-04 16:26 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-64630?
When was CVE-2026-64630 disclosed?
Is CVE-2026-64630 actively exploited?
What is the CVSS score of CVE-2026-64630?
How do I remediate CVE-2026-64630?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64630
Is Your Infrastructure Affected by CVE-2026-64630?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.