VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

io.ktor:ktor-client-cio: vulnerability history, versions and safety

io.ktor:ktor-client-cio is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 21 releases, first recorded in Jan 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all io.ktor:ktor-client-cio vulnerabilities

Vulert verdict on io.ktor:ktor-client-cio 3.6.0 i

Updated on 23 Oct 2026

Good news: 3.6.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 3.6.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.6.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.6.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 27 Jan 2020 i
  • Highest CVSS 5.4 i
  • With no published fix 0 i
  • Depended on by 328 packages i
  • Stars 14,549 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for io.ktor:ktor-client-cio, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.6.0 16 Sep 2026 none Apache-2.0 — Details →
3.5.2 31 Jul 2026 none Apache-2.0 — Details →
3.5.1 25 Jun 2026 none Apache-2.0 — Details →
3.5.0 14 May 2026 none Apache-2.0 — Details →
3.4.3 22 Apr 2026 none Apache-2.0 — Details →
3.4.2 27 Mar 2026 none Apache-2.0 — Details →
3.2.4 11 Mar 2026 none Apache-2.0 — Details →
3.4.1 03 Mar 2026 none Apache-2.0 — Details →
3.4.0 22 Jan 2026 none Apache-2.0 — Details →
3.3.3 26 Nov 2025 none Apache-2.0 — Details →
3.3.2 05 Nov 2025 none Apache-2.0 — Details →
3.3.1 08 Oct 2025 none Apache-2.0 — Details →
3.3.0 11 Sep 2025 none Apache-2.0 — Details →
3.2.3 29 Jul 2025 none Apache-2.0 — Details →
3.2.2 14 Jul 2025 none Apache-2.0 — Details →
3.2.1 03 Jul 2025 none Apache-2.0 — Details →
3.2.0 12 Jun 2025 none Apache-2.0 — Details →
3.1.3 05 May 2025 none Apache-2.0 — Details →
3.1.2 27 Mar 2025 none Apache-2.0 — Details →
3.1.1 24 Feb 2025 none Apache-2.0 — Details →
3.1.0 11 Feb 2025 none Apache-2.0 — Details →
3.0.3 18 Dec 2024 none Apache-2.0 — Details →
3.0.2 03 Dec 2024 none Apache-2.0 — Details →
2.3.13 19 Nov 2024 none Apache-2.0 — Details →
3.0.1 29 Oct 2024 none Apache-2.0 — Details →
3.0.0 09 Oct 2024 none Apache-2.0 — Details →
3.0.0-rc-2 02 Oct 2024 none Apache-2.0 — Details →
3.0.0-rc-1 09 Sep 2024 none Apache-2.0 — Details →
3.0.0-beta-2 15 Jul 2024 none Apache-2.0 — Details →
2.3.12 20 Jun 2024 none Apache-2.0 — Details →
2.3.11 08 May 2024 none Apache-2.0 — Details →
2.3.10 08 Apr 2024 none Apache-2.0 — Details →
2.3.9 04 Mar 2024 none Apache-2.0 — Details →
2.3.8 31 Jan 2024 none Apache-2.0 — Details →
2.3.7 07 Dec 2023 none Apache-2.0 — Details →
3.0.0-beta-1 23 Nov 2023 none Apache-2.0 — Details →
2.3.6 06 Nov 2023 none Apache-2.0 — Details →
2.3.5 04 Oct 2023 none Apache-2.0 — Details →
2.3.4 31 Aug 2023 none Apache-2.0 — Details →
2.3.3 01 Aug 2023 none Apache-2.0 — Details →
2.3.2 28 Jun 2023 none Apache-2.0 — Details →
2.3.1 31 May 2023 none Apache-2.0 — Details →
2.3.0 19 Apr 2023 none Apache-2.0 — Details →
2.2.4 28 Feb 2023 none Apache-2.0 — Details →
2.2.3 31 Jan 2023 none Apache-2.0 — Details →
2.2.2 03 Jan 2023 none Apache-2.0 — Details →
2.2.1 07 Dec 2022 none Apache-2.0 — Details →
2.2.0 07 Dec 2022 none Apache-2.0 — Details →
2.1.3 28 Oct 2022 none Apache-2.0 — Details →
2.1.2 29 Sep 2022 none Apache-2.0 — Details →
2.1.1 06 Sep 2022 none Apache-2.0 — Details →
2.1.0 10 Aug 2022 none Apache-2.0 — Details →
2.0.3 28 Jun 2022 none Apache-2.0 — Details →
2.0.2 27 May 2022 none Apache-2.0 — Details →
2.0.1 28 Apr 2022 none Apache-2.0 — Details →
2.0.0 08 Apr 2022 none Apache-2.0 — Details →
2.0.0-rc-1 04 Apr 2022 none Apache-2.0 — Details →
1.6.8 14 Mar 2022 none Apache-2.0 — Details →
2.0.0-beta-1 22 Dec 2021 none Apache-2.0 — Details →
1.6.7 07 Dec 2021 none Apache-2.0 — Details →
1.6.6 26 Nov 2021 none Apache-2.0 — Details →
1.6.5 01 Nov 2021 none Apache-2.0 — Details →
1.6.4 30 Sep 2021 none Apache-2.0 — Details →
1.6.3 25 Aug 2021 none Apache-2.0 — Details →
1.6.2 28 Jul 2021 none Apache-2.0 — Details →
1.6.1 30 Jun 2021 none Apache-2.0 — Details →
1.6.0 27 May 2021 none Apache-2.0 — Details →
1.5.4 29 Apr 2021 none Apache-2.0 — Details →
1.5.3 02 Apr 2021 none Apache-2.0 — Details →
1.5.2 25 Feb 2021 none Apache-2.0 — Details →
1.5.1 27 Jan 2021 none Apache-2.0 — Details →
1.5.0 21 Dec 2020 none Apache-2.0 — Details →
1.4.3 01 Dec 2020 none Apache-2.0 — Details →
1.4.2 10 Nov 2020 none Apache-2.0 — Details →
1.4.1 24 Sep 2020 none Apache-2.0 — Details →
1.4.0 18 Aug 2020 none Apache-2.0 — Details →
1.3.2-1.4.0-rc 10 Aug 2020 none Apache-2.0 — Details →
1.3.1 26 Feb 2020 none Apache-2.0 — Details →
1.3.0 14 Jan 2020 none Apache-2.0 — Details →
1.3.0-rc2 28 Dec 2019 L1 Apache-2.0 Yes Details →
1.3.0-rc 19 Dec 2019 L1 Apache-2.0 Yes Details →
1.2.6 21 Nov 2019 L1 Apache-2.0 Yes Details →
1.2.5 23 Oct 2019 L1 Apache-2.0 Yes Details →
1.2.4 02 Sep 2019 L1 Apache-2.0 Yes Details →
1.2.3 01 Aug 2019 L1 Apache-2.0 Yes Details →
1.2.3-rc 23 Jul 2019 L1 Apache-2.0 Yes Details →
1.2.2 20 Jun 2019 L1 Apache-2.0 Yes Details →
1.2.1 27 May 2019 L1 Apache-2.0 Yes Details →
1.2.0 14 May 2019 L1 Apache-2.0 Yes Details →
1.2.0-rc2 08 May 2019 L1 Apache-2.0 Yes Details →
1.2.0-rc 30 Apr 2019 L1 Apache-2.0 Yes Details →
1.1.5 24 Apr 2019 L1 Apache-2.0 Yes Details →
1.1.4 15 Apr 2019 L1 Apache-2.0 Yes Details →
1.1.3 21 Feb 2019 L1 Apache-2.0 Yes Details →
1.1.2 24 Jan 2019 L1 Apache-2.0 Yes Details →
1.1.1 26 Dec 2018 L1 Apache-2.0 Yes Details →
1.1.0 24 Dec 2018 L1 Apache-2.0 Yes Details →
1.0.1 04 Dec 2018 L1 Apache-2.0 Yes Details →
1.0.0 19 Nov 2018 L1 Apache-2.0 Yes Details →
1.0.0-rc 15 Nov 2018 L1 Apache-2.0 Yes Details →

All 100 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for io.ktor:ktor-client-cio

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-5207: Open Source Vulnerability in io.ktor:ktor-client-cio and io.ktor:ktor-server-cio 5.4 low 1.3.0 27 Jan 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About io.ktor:ktor-client-cio

Is io.ktor:ktor-client-cio safe to use?

Vulert records 1 vulnerabilities for io.ktor:ktor-client-cio in Maven: 0 critical, 0 high, 0 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is io.ktor:ktor-client-cio's Vulert package health score?

Vulert scores io.ktor:ktor-client-cio 84/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of io.ktor:ktor-client-cio affected?

No. 3.6.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of io.ktor:ktor-client-cio should I use?

3.6.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does io.ktor:ktor-client-cio have?

1 vulnerability is recorded for io.ktor:ktor-client-cio in the Maven ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new io.ktor:ktor-client-cio vulnerabilities disclosed?

0 vulnerabilities were recorded for io.ktor:ktor-client-cio in the last 12 months, and the oldest entry in this database dates to 27 Jan 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of io.ktor:ktor-client-cio are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor io.ktor:ktor-client-cio for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the io.ktor:ktor-client-cio version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.