CVE-2026-64813

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
10.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: 10.0Exploit: 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 settings modification was possible in a Remote Development session

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

Published

July 23, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 24, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-64813(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 20× in last 7d / 20× 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-27 11:59 UTCGHSA enrichment
  2. 2026-07-27 08:15 UTCGHSA enrichment
  3. 2026-07-27 04:31 UTCGHSA enrichment
  4. 2026-07-27 00:45 UTCGHSA enrichment
  5. 2026-07-26 20:59 UTCGHSA enrichment
  6. 2026-07-26 17:14 UTCEG score recompute
  7. 2026-07-26 17:14 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 13:30 UTCEG score recompute
  11. 2026-07-26 13:30 UTCGHSA enrichment
  12. 2026-07-26 09:45 UTCGHSA enrichment
  13. 2026-07-26 03:09 UTCEG score recompute
  14. 2026-07-26 03:09 UTCGHSA enrichment
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-24 14:18 UTCEPSS rescore
  18. 2026-07-24 14:18 UTCEPSS rescore
  19. 2026-07-23 12:15 UTCEG score recompute
  20. 2026-07-23 12:14 UTCMITRE cvelistV5first tracked

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-64813?

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