Skip to main content
← Vulnerabilities

In JetBrains Ktor before 3.6.1 session forgery was possible via tampered encrypted session cookies

8.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.6.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.6.1.

Published
Last modified
11/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

In JetBrains Ktor before 3.6.1 session forgery was possible via tampered encrypted session cookies

cve.now Index

11Pcve.now Index 11 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.1/10CVSS 8.1
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.6.1.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • JetBrains Ktor

    fixed in 3.6.1

Evidence 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123317

Is CVE-2026-123317 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-123317?

Ktor: before 3.6.1.Source: cve.now feed data

How do I fix CVE-2026-123317?

Upgrade to a fixed version: 3.6.1.Source: cve.now feed data