In JetBrains IntelliJ IDEA before 2026.2 arbitrary code execution was possible before granting project trust via development container configuration
CVE-2026-64811
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 24, 2026
Advisory Details (1)
Auto-updated Jul 23, 2026Vendor Advisories for CVE-2026-64811(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 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.
- 2026-07-27 15:08 UTCGHSA enrichment
- 2026-07-27 03:08 UTCGHSA enrichment
- 2026-07-26 15:09 UTCEG score recompute
- 2026-07-26 15:09 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:09 UTCEG score recompute
- 2026-07-26 03:09 UTCGHSA enrichment
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 12:15 UTCEG score recompute
- 2026-07-23 12:14 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-829
- CVE-2021-41037EG 10.0CRITICAL
- CVE-2022-1161EG 10.0EPSS p91CRITICAL
- CVE-2020-4561EG 10.0CRITICAL
- CVE-2022-24119EG 9.8CRITICAL
- CVE-2020-16152EG 9.8EPSS p98CRITICAL
- CVE-2021-21804EG 9.8CRITICAL
- CVE-2020-25414EG 9.8CRITICAL
- CVE-2020-3794EG 9.8EPSS p93CRITICAL
- CVE-2020-8128EG 9.8CRITICAL
- CVE-2012-4919EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-64811?
When was CVE-2026-64811 disclosed?
Is CVE-2026-64811 actively exploited?
What is the CVSS score of CVE-2026-64811?
How do I remediate CVE-2026-64811?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-64811
Is Your Infrastructure Affected by CVE-2026-64811?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.