CVE-2026-32745
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains Datalore before 2026.1 session hijacking was possible due to missing secure attribute for cookie settings
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn JetBrains Datalore before version 2026.1, session cookies were missing the Secure attribute, allowing them to be transmitted over unencrypted HTTP connections. This could enable session hijacking through man-in-the-middle attacks where attackers intercept session cookies sent over insecure channels.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Datalore versionIdentify the installed JetBrains Datalore version by accessing the application admin panel, checking the installation directory metadata, or running 'datalore --version' if a CLI is availableAffected if version is below 2026.1
-
Confirm HTTP listener is activeVerify that Datalore is accessible over HTTP (port 80) or that HTTP-to-HTTPS redirection is not enforced, by attempting an HTTP connection to the serverAffected if HTTP connections are allowed and the application is reachable over an unencrypted connection
-
Inspect session cookie for Secure flagCapture an HTTP request to Datalore using browser developer tools or a network proxy, then examine the Set-Cookie headers for session cookies to determine if the Secure attribute is presentAffected if session cookies do not contain the Secure attribute in their Set-Cookie headers
You are affected if running Datalore version below 2026.1 with HTTP access enabled and session cookies lacking the Secure attribute.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.1
Configure all session cookies with the Secure attribute to ensure they are only transmitted over HTTPS connections, and consider implementing HSTS headers.
2026.1
- Review JetBrains Datalore 2026.1 release notes for any migration requirements
- Ensure all running notebooks and data processing jobs are saved and stopped
- Create a backup of the Datalore installation directory and any custom configurations
- Upgrade Datalore to version 2026.1 or later by installing the new version from the official JetBrains website or using your existing update mechanism
- After upgrade, verify that the 'Secure' attribute is set on session cookies by inspecting HTTP response headers in the browser developer tools or using a web proxy
- Confirm that session authentication functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32745 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32745 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data