How severe is CVE-2022-2576?

CVE-2022-2576 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-2576?

CVE-2022-2576 affects the following packages: org.eclipse.californium:californium-core (Maven), org.eclipse.californium:californium-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-2576?

Update org.eclipse.californium:californium-core to 2.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2576 is resolved across your whole dependency graph.

How do I detect CVE-2022-2576 in my Maven dependencies?

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

How do I mitigate CVE-2022-2576 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-2576 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-2576, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-2576?

CVE-2022-2576 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-2576?

CVE-2022-2576 is classified as CWE-408 (CWE-408). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-2576 published, and has it been updated?

CVE-2022-2576 was published on July 29, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2022-2576 — californium-core

HIGHFix: eclipse-californium/californium#2039

CVE-2022-2576 is a high-severity (CVSS 7.5) CWE-408 vulnerability in org.eclipse.californium:californium-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.eclipse.californium:californium-core — see the affected versions and patch details below.

Eclipse Californium denial of service (DoS) via Datagram Transport Layer Security (DTLS) handshake on parameter mismatch

Also known asGHSA-qq3j-44gw-cf6r

Published

Jul 29, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

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

2 pkgs affected

☕org.eclipse.californium:californium-core☕org.eclipse.californium:californium-core

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 Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.eclipse.californium:californium-core`	≥ 2.0.0&&< 2.7.3	2.7.3`org.eclipse.californium:californium-core:2.7.3`
☕Maven	`org.eclipse.californium:californium-core`	≥ 3.0.0&&< 3.6.0	3.6.0`org.eclipse.californium:californium-core:3.6.0`

Affected Products

1 product · 2 configurations

Application

californiumeclipse

≥ 3.0.0 && ≤ 3.5.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS res…

bugs.eclipse.orgNVDAug 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.californium:californium-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.californium:californium-core to 2.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2576 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-2576 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-408CWE-408

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jul 29, 2022

First exploit

Aug 5, 2022

7 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-2576

GHSA-qq3j-44gw-cf6r

References

Advisorygithub.com · CVE 2022 2576.json Advisorynvd.nist.gov · CVE 2022 2576 Webbugs.eclipse.org Webgithub.com Webgithub.com · 0cc953a1dc071efc960130e229fcb4f8bda7f9df Webgithub.com · 8373db84b2d07f22c39ffc333ab881dba9401722 Packagegithub.com · californium

Related vulnerabilities

This CVE is high severity; 1 of 3 other CVEs with CWE-408 is rated as high or higher (top: high).

CVE-2026-41374CVE-2026-41331CVE-2026-41405Browse all CWE-408

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-2576 — californium-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-2576 in your dependencies?