JetBrains Ktor denial of service via infinite loop in CIO engine
- Exploited
- No known exploitation
- Fix
- Fixed in 3.6.1
- Who is exposed
- Not reported
Summary
In JetBrains Ktor before 3.6.1 a DoS attack was possible via the CIO engine
What to do
Upgrade to a fixed version: 3.6.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133255 (In JetBrains Ktor before 3.6.1 a DoS attack was possible via the CIO engine), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133255 (entry last updated 2026-11-19):
Affected:
- JetBrains Ktor: fixed in 3.6.1
Fixed versions: 3.6.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133255 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133255 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.jetbrains.com/privacy-security/issues-fixed/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133255
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133255"}.Affected versions
- JetBrains Ktorfixed in 3.6.1
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jetbrains.com · privacy-security/issues-fixed |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133255 |
| Record | NVD · CVE-2026-133255 |
Questions about CVE-2026-133255
Is CVE-2026-133255 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-133255?
Ktor: before 3.6.1.
Source: cve.now feed data
How do I fix CVE-2026-133255?
Upgrade to a fixed version: 3.6.1.
Source: cve.now feed data
Related
- CVE-2022-29930SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value.
- CVE-2023-45612In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE
- CVE-2026-123317In JetBrains Ktor before 3.6.1 session forgery was possible via tampered encrypted session cookies
- CVE-2022-48476In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible
- CVE-2023-45613In JetBrains Ktor before 2.3.5 server certificates were not verified
- CVE-2026-68762In JetBrains Ktor before 3.4.1 potential DoS attack via WebSocket decompression was possible
No corrections so far. Something wrong on this page? Report an error.