NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

JetBrain Ktor before 2.1.0 vulnerable to selection of wrong authentication providerGHSA-hccx-cg4v-hrjx

MEDIUMFix: ktorio/ktor#3092

GHSA-hccx-cg4v-hrjx is a medium-severity (CVSS 6.5) Improper Authentication vulnerability in io.ktor:ktor. A fix is available for io.ktor:ktor — see the affected versions and patch details below.

Also known asCVE-2022-38180
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.42%0.84%1.26%0.0%0.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕io.ktor:ktor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.ktor:ktorall versions2.1.0io.ktor:ktor:2.1.0

Affected Products

1 product · 1 configurations
Application
ktorjetbrains
< 2.1.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.ktor:ktor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.ktor:ktor to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hccx-cg4v-hrjx is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

In JetBrains Ktor before 2.1.0 the wrong authentication provider could be selected in some cases
O3 Security · Impact-Aware SCA

Is GHSA-hccx-cg4v-hrjx in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
JetBrain Ktor before 2.1.0 vulnerable to selection of wrong…