VulnerabilityPublished 13 Mar 2026Updated 17 Mar 2026

CVE-2026-32745: JetBrains Datalore · CWE-614

Affects JetBrains DataloreSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2026.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2026.1

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade JetBrains Datalore to 2026.1.

Affected software

Product	Affected	Fixed in
JetBrainsDatalore	Affected <2026.1	Fixed in 2026.1

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade JetBrains Datalore to version 2026.1 or later, where the secure cookie attribute issue is resolved. In the interim, enforce HTTPS strictly across all Datalore access points to prevent cookies from being transmitted over unencrypted channels. Implement HTTP Strict Transport Security (HSTS) headers to ensure browsers only connect via HTTPS. Review and configure web server and application settings to explicitly set the 'Secure' and 'HttpOnly' flags on all session cookies. Conduct network segmentation and monitoring to detect suspicious activities indicative of session hijacking attempts. Educate users about the risks of using public or untrusted networks and encourage VPN usage. Additionally, consider implementing multi-factor authentication (MFA) on Datalore accounts to reduce the impact of compromised sessions. Regularly audit and monitor session management practices and logs for anomalies. Finally, stay informed on JetBrains security advisories for any patches or updates related to this vulnerability.

Description

In JetBrains Datalore before 2026.1 session hijacking was possible due to missing secure attribute for cookie settings

Impact

The primary impact of this vulnerability is the compromise of user session confidentiality through session hijacking. Attackers who can intercept network traffic, such as those on public Wi-Fi or internal networks, can steal session cookies and gain unauthorized access to user accounts within Datalore. This can lead to unauthorized data access, exposure of sensitive analytics or code, and potential misuse of the platform under the victim's identity. Although integrity and availability impacts are low or none, the confidentiality breach can have significant consequences in environments handling proprietary or sensitive data. Organizations relying on Datalore for collaborative data science or software development may face data leakage risks. The requirement for user interaction and adjacent network access limits the attack scope but does not eliminate risk, especially in remote work or hybrid environments where network security varies. The absence of known exploits reduces immediate risk but does not preclude future exploitation. Overall, the vulnerability can undermine trust in the platform and lead to compliance issues if sensitive data is exposed.

CWE-614Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The Secure attribute for sensitive cookies in HTTPS sessions is not set.
Implementation
Always set the secure attribute when the cookie should be sent via HTTPS only.
OWASP Cheat Sheets
Cross-Site Request Forgery Prevention (opens in a new tab)
Session Management (opens in a new tab)
OWASP ASVS 4.0.3
V3.4.1 (opens in a new tab)
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 23:16 UTC

WeaknessesCWE-614

Technical details

References

Community reviews

Related threats