CVE-2026-64814

HIGHPre-NVD 8.68.6—
EchelonGraph scoreHIGH confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. a secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

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

In JetBrains IntelliJ IDEA before 2026.2 unauthorized file access was possible in a Remote Development session

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
54(Track)
EG Risk 54/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
Severity86% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated Jul 23, 2026
No patch confirmed yet.
generic

Fixed security issues

https://www.jetbrains.com/privacy-security/issues-fixed/

Vendor Advisories for CVE-2026-64814(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 28× 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.

  1. 2026-08-03 20:48 UTCEG score recompute
  2. 2026-08-03 20:48 UTCGHSA enrichment
  3. 2026-08-03 10:36 UTCEPSS rescore
  4. 2026-08-03 08:33 UTCGHSA enrichment
  5. 2026-08-02 20:19 UTCGHSA enrichment
  6. 2026-08-02 08:04 UTCEG score recompute
  7. 2026-08-02 08:04 UTCGHSA enrichment
  8. 2026-08-02 02:27 UTCEPSS rescore
  9. 2026-08-01 19:49 UTCGHSA enrichment
  10. 2026-08-01 07:34 UTCEG score recompute
  11. 2026-08-01 07:34 UTCGHSA enrichment
  12. 2026-08-01 04:16 UTCEPSS rescore
  13. 2026-07-31 19:19 UTCGHSA enrichment
  14. 2026-07-31 07:03 UTCGHSA enrichment
  15. 2026-07-30 18:49 UTCEG score recompute
  16. 2026-07-30 18:49 UTCGHSA enrichment
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 06:15 UTCEG score recompute
  19. 2026-07-30 06:15 UTCGHSA enrichment
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-29 17:58 UTCGHSA enrichment
  23. 2026-07-29 05:43 UTCGHSA enrichment
  24. 2026-07-28 17:26 UTCGHSA enrichment
  25. 2026-07-28 16:48 UTCEG score recompute
Show 19 more
  1. 2026-07-28 16:48 UTCGHSA enrichment
  2. 2026-07-28 15:37 UTCEPSS rescore
  3. 2026-07-28 04:09 UTCGHSA enrichment
  4. 2026-07-27 15:55 UTCEG score recompute
  5. 2026-07-27 15:54 UTCGHSA enrichment
  6. 2026-07-27 14:14 UTCEPSS rescore
  7. 2026-07-27 03:39 UTCGHSA enrichment
  8. 2026-07-26 15:23 UTCEG score recompute
  9. 2026-07-26 15:23 UTCGHSA enrichment
  10. 2026-07-26 14:54 UTCEPSS rescore
  11. 2026-07-26 14:54 UTCEPSS rescore
  12. 2026-07-26 03:09 UTCEG score recompute
  13. 2026-07-26 03:09 UTCGHSA enrichment
  14. 2026-07-25 14:18 UTCEPSS rescore
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-24 14:18 UTCEPSS rescore
  17. 2026-07-24 14:18 UTCEPSS rescore
  18. 2026-07-23 12:15 UTCEG score recompute
  19. 2026-07-23 12:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64814?
CVE-2026-64814 is a high vulnerability published on July 23, 2026. In JetBrains IntelliJ IDEA before 2026.2 unauthorized file access was possible in a Remote Development session
When was CVE-2026-64814 disclosed?
CVE-2026-64814 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64814 actively exploited?
CVE-2026-64814 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 76.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64814?
CVE-2026-64814 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-64814?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64814, 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-64814

Explore →

Is Your Infrastructure Affected by CVE-2026-64814?

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

Start Free Scan →Browse All CVEs