Skip to main content

Datalore EUVDEUVD-2026-12045

| CVE-2026-32745 MEDIUM
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614)
2026-03-13 JetBrains
6.3
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A02:2025 - Security Misconfiguration
ASVS 5.0
V3 - Web Frontend Security Secure cookie flag
Impact

The CVSS:3.1 vector (AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N) indicates moderate overall severity but notable practical constraints: attack vector is Adjacent (local network only), which significantly limits widespread exploitation compared to network-accessible vulnerabilities. Attack complexity is Low and no privileges are required, but User Interaction is required (victim must visit attacker-controlled content or be on compromised network). Confidentiality impact is High (full session compromise), Integrity is Low (limited to session scope), and Availability is None. The real-world risk is contextual: in air-gapped environments or cloud-hosted Datalore instances, this is lower priority; in shared corporate networks or public WiFi scenarios, it becomes substantially more critical. No publicly disclosed POC or KEV status is indicated in provided intelligence, suggesting this may be a responsibly-disclosed researcher finding rather than actively exploited in the wild. SSVC assessment: exploitation is Likely (session interception is straightforward with network access), automatable (can be scripted), and technical impact is total (full account compromise), but this is only feasible for authenticated users on the attacker's network segment.

Exploit ScenarioDerived

An attacker positioned on the same local network (corporate WiFi, shared office network, or compromised router) performs passive network sniffing using tools like tcpdump or Wireshark. When a legitimate Datalore user initiates an HTTP (non-HTTPS) connection or when the application transmits session cookies without the Secure flag, the attacker captures the session cookie in cleartext. The attacker then replays this cookie in their own HTTP requests to the Datalore instance, gaining full authenticated access to the victim's account without knowing their password. If Datalore is hosted behind HTTPS, the attack requires the user to click a phishing link to an HTTP variant of the site (AV:A/UI:R satisfied). The attacker gains high confidentiality impact by accessing sensitive data/notebooks and limited integrity impact by modifying session state. No POC is noted in current intelligence, but cookie interception is a well-understood technique and readily automatable.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 13, 2026

JetBrains Datalore versions before 2026.1 contain a session hijacking vulnerability (CVE-2026-32745) caused by missing secure attribute configuration on session cookies, allowing attackers on the same network to intercept and reuse session tokens. The vulnerability affects all Datalore versions prior to 2026.1 and requires adjacent network access combined with user interaction; while the CVSS score is moderate (6.3), the impact is high for confidentiality and enables unauthorized account access.

RemediationAI

Upgrade JetBrains Datalore to version 2026.1 or later (https://www.jetbrains.com/privacy-security/issues-fixed/) Mitigation (Pre-Patch): Enforce HTTPS-only connections to Datalore instances via reverse proxy (nginx/Apache with HSTS header 'Strict-Transport-Security: max-age=31536000; includeSubDomains') Mitigation (Pre-Patch): Restrict network access to Datalore instances using firewall rules to trusted networks only, reducing attack surface to adjacent network threat actors Mitigation (Pre-Patch): Implement VPN or network segmentation to isolate Datalore deployment from untrusted network segments Detection: Monitor HTTP access logs for unencrypted session cookie transmission; implement network IDS rules to detect cookie interception patterns on local network segments

Affected VersionsENISA

Datalore 0 <2026.1

Affected Packages

euvd datalore fix: 2026.1

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability (CWE-614: Insecure Cookie Transmission) involves improper HTTP cookie security configuration in JetBrains Datalore's session management implementation. The missing 'Secure' flag on session cookies allows them to be transmitted over unencrypted HTTP connections or intercepted by network-level attacks (ARP spoofing, MITM on local networks). The affected product is identified via CPE: cpe:2.3:a:jetbrains:datalore:*:*:*:*:*:*:*:* (all versions). The root cause is insufficient hardening of cookie attributes; proper remediation requires setting the Secure flag to enforce HTTPS-only transmission, supplemented by HttpOnly and SameSite flags to prevent XSS-based theft and CSRF attacks respectively.

Know when Datalore gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 6.3 MEDIUM
AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
2026.1
CVE Published
Mar 13, 2026 - 15:50 nvd
MEDIUM 6.3

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

Organizations using JetBrains Datalore should be aware of moderate risk from CVE-2026-32745 rated CVSS 6.3. Exploitation could compromise the security of affected deployments. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 100% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
Low

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy