Cyber Resilience

CVE-2026-64813

Jetbrains Intellij Idea ≤ 2026.2

Published
23 July 2026
Modified
28 July 2026
Patch / advisory
CVSS Score v3.1 10.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0039 32th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2026-64813 is a critical-severity Client-Side Enforcement of Server-Side Security (CWE-602) vulnerability in Jetbrains Intellij Idea. Its CVSS base score is 10.0 (Critical).

Operationally, ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-17 (Remote Access) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In JetBrains IntelliJ IDEA before 2026.2 unauthorized settings modification was possible in a Remote Development session

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

Insufficient information to map techniques.
Confidence: LOW · MITRE ATT&CK Enterprise v19.0

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1068 Exploitation for Privilege Escalation Privilege Escalationconfidence: MEDIUM
Client-side enforcement flaw allows unauthorized settings changes in remote session, enabling privilege escalation.
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-46970Same product: Jetbrains Intellij Idea
CVE-2024-24941Same product: Jetbrains Intellij Idea
CVE-2023-38069Same product: Jetbrains Intellij Idea
CVE-2024-24940Same product: Jetbrains Intellij Idea
CVE-2026-49366Same product: Jetbrains Intellij Idea
CVE-2026-49383Same product: Jetbrains Intellij Idea
CVE-2026-64811Same product: Jetbrains Intellij Idea
CVE-2026-64812Same product: Jetbrains Intellij Idea
CVE-2026-41882Same product: Jetbrains Intellij Idea
CVE-2023-51655Same product: Jetbrains Intellij Idea

Affected Assets

jetbrains
intellij idea
≤ 2026.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-17 Remote Access
  • CM-5 Access Restrictions for Change
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V10.7.1
  • V2.2.2
  • V8.3.1
  • V10.4.1

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces server-side access decisions so that settings cannot be modified by an unauthorized remote client.

prevent

Requires explicit authorization, monitoring, and usage restrictions for all remote development sessions that could otherwise allow client-driven settings changes.

prevent

Restricts the ability to change configuration settings to only authorized roles, mitigating the client-side bypass described in the CVE.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent design flaws that place server security enforcement on the client.

PR.AA-05 partial match
prevents

Proper policy-based enforcement of authorizations implies server-side controls rather than client-only checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure architecture principles discourage client-side trust but do not directly address this weakness.

detects

Security testing can detect client-side enforcement but is not the primary mitigation.

prevents

Information access restriction is undermined when the client is trusted to enforce it.

prevents

Secure development lifecycle mandates server-side validation and prevents reliance on client enforcement.

prevents

Application security requirements explicitly call for server-side enforcement of security mechanisms.

prevents

Secure coding standards require server-side checks and reject client-only enforcement.

References