CVE-2022-39368 is a denial of service in the DTLS layer of Eclipse Californium before 3.7.0 and 2.7.4: failed handshakes never release the throttling counters, so once the threshold is reached the stack drops records permanently. NVD and GitHub score it 8.2. Update to Californium 3.7.0 or 2.7.4; there is no workaround.
Vulnerability summary
CVSS base score
8.2
High severity
EPSS score (FIRST)
0.7%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2022-39368 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Eclipse Californium (Scandium DTLS) | cpe:2.3:a:eclipse:californium:*:*:*:*:*:*:*:* | before 2.7.4, and 3.0.0 to before 3.7.0; fixed in 2.7.4 and 3.7.0 (GHSA-p72g-cgh9-ghjg, NVD) |
| Eclipse Leshan (LwM2M, bundles Californium) | — | 1.0.0 to 1.4.1 and 2.0.0-M1 to 2.0.0-M8, any DTLS usage (Leshan security policy) |
What does this mean for affected devices?
NVD's description: "Failing handshakes don't cleanup counters for throttling, causing the threshold to be reached without being released again. This results in permanently dropping records." NVD's Primary score is 8.2, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H, the same as the score from GitHub, the CNA. Both list CWE-404 (improper resource shutdown or release) and CWE-459 (incomplete cleanup). The CPE configuration covers Californium before 2.7.4 and 3.0.0 up to 3.7.0, and the record was published on 2022-11-10 (NVD, CVE record).
How does the bug trigger?
The Californium advisory GHSA-p72g-cgh9-ghjg says the issue "was reported for certificate based handshakes, but it can't be excluded, that this happens also for PSK based handshakes", and that it "generally affects client and server as well." The original report, issue 2065, describes Scandium 3.6.0 running as a DTLS server: the client answered a CertificateRequest with one datagram of four records starting with an empty Certificate record. The connection's executor shut down on the handshake error, and the pending-jobs counter was decremented four times but incremented only once. The advisory's summary of the result is that the throttling threshold "may get reached and will not be released again", which ends in permanently dropped records.
Which versions fix it?
The advisory, published on 2022-11-09, covers the Maven artifact org.eclipse.californium:scandium and asks users to update to 3.7.0, or to 2.7.4 if Californium 2 support is required. It lists no workarounds. Californium's security policy lists the bug as "Failing DTLS handshake" for versions below 3.7 and 2.7.4. The ranges differ by source: GitHub's CVE record lists 2.7.0 to before 2.7.4 and 3.0.0 to before 3.7.0, while NVD's CPE covers every version before 2.7.4, and Leshan counts its 1.x releases, which bundle Californium 2.x, as affected from 1.0.0. Treat any Californium 2.x release before 2.7.4 as affected.
Which devices are affected?
Any gateway or service that terminates DTLS with Californium, including LwM2M servers built on Eclipse Leshan. Leshan's security policy lists CVE-2022-39368 for Leshan 1.0.0 to 1.4.1 and 2.0.0-M1 to 2.0.0-M8, for "any DTLS usage", and names 1.5.0 and 2.0.0-M13 and later as free of known vulnerabilities. A server that drops records stops serving the devices whose DTLS traffic it drops. Our CoAP security guide covers DTLS deployment. The earlier Californium flaw CVE-2021-34433 skipped a signature check in the same handshake code, and CVE-2020-3162 stopped the CoAP server in Cisco IoT Field Network Director.
CVE-2022-39368 is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00735, the 55.1st percentile, in the 2026-11-17 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: Californium before 3.7.0 and 2.7.4, failing handshakes do not clean up throttling counters, records permanently dropped; [email protected] Primary CVSS 3.1 8.2 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H; [email protected] 8.2 same vector; CWE-404, CWE-459; CPE < 2.7.4 and 3.0.0 to < 3.7.0; published 2022-11-10. — NVD
- GHSA-p72g-cgh9-ghjg (published 2022-11-09), package org.eclipse.californium:scandium, patched 2.7.4 and 3.7.0: reported for certificate based handshakes, PSK cannot be excluded, affects client and server; update to 3.7.0 or 2.7.4; workarounds none. — Eclipse Californium security advisory
- Issue 2065: Scandium 3.6.0 DTLS server; client responds to CertificateRequest with a datagram of 4 records starting with an invalid Certificate record; serial executor shuts down; pendingInboundJobsCountdown decremented 4 times, incremented once. — Eclipse Californium on GitHub
- Californium security policy: "< 3.7, < 2.7.4 Failing DTLS handshake CVE-2022-39368". — Eclipse Californium security policy
- Leshan security policy: CVE-2022-39368 affects Leshan 2.0.0-M1 -> 2.0.0-M8 and 1.0.0 -> 1.4.1 via californium/scandium, any DTLS usage; versions not affected by known vulnerabilities: 2.0.0-M13+ and 1.5.0+. — Eclipse Leshan security policy
- CVE record (CNA GitHub): californium >= 2.7.0, < 2.7.4 and >= 3.0.0, < 3.7.0 affected. — CVE.org
- Not in the CISA KEV catalog, version 2026.11.17 (1,782 entries), checked 2026-11-18. — CISA KEV
- EPSS 0.00735, percentile 0.55061, dataset 2026-11-17, read 2026-11-18. — FIRST EPSS

Related advisories
Sources
- NVD
- CVE.org record CVE-2022-39368 (CNA: GitHub)
- Eclipse Californium advisory GHSA-p72g-cgh9-ghjg: Failing DTLS handshakes may cause throttling to block processing of records
- Eclipse Californium issue 2065
- Eclipse Californium security policy (known vulnerabilities)
- Eclipse Leshan security policy (versions security state)
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which Californium versions fix CVE-2022-39368?
Californium 3.7.0, or 2.7.4 for users who need the 2.x line. The advisory lists no workaround (per GHSA-p72g-cgh9-ghjg and NVD).
Are PSK-based DTLS handshakes affected by CVE-2022-39368?
Possibly. The bug was reported for certificate-based handshakes, but the Californium advisory says it cannot be excluded for PSK handshakes, and it affects both clients and servers (per GHSA-p72g-cgh9-ghjg).
Is Eclipse Leshan affected by CVE-2022-39368?
Yes, through the bundled Californium Scandium library: Leshan 1.0.0 to 1.4.1 and 2.0.0-M1 to 2.0.0-M8, for any DTLS usage. Leshan 1.5.0 and 2.0.0-M13 and later carry no known vulnerability (per the Leshan security policy).
Is CVE-2022-39368 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-18 (catalog version 2026.11.17). FIRST EPSS gives it 0.00735, the 55.1st percentile, in the 2026-11-17 dataset (per CISA KEV and FIRST EPSS).
Questions about this page?