What is CVE-2025-12383?

CVE-2025-12383 is a critical-severity race condition vulnerability in org.glassfish.jersey.core:jersey-client (maven), affecting versions = 2.45. It is fixed in 2.46, 3.0.17, 3.1.10. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

Which versions of org.glassfish.jersey.core:jersey-client are affected by CVE-2025-12383?

org.glassfish.jersey.core:jersey-client (maven) versions = 2.45 is affected.

Is there a fix for CVE-2025-12383?

Yes. CVE-2025-12383 is fixed in 2.46, 3.0.17, 3.1.10. Upgrade to this version or later.

Is CVE-2025-12383 exploitable, and should I be worried?

Whether CVE-2025-12383 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-12383 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-12383

Q: How do I fix CVE-2025-12383?

Upgrade: org.glassfish.jersey.core:jersey-client to 2.46 or later, org.glassfish.jersey.core:jersey-client to 3.0.17 or later, org.glassfish.jersey.core:jersey-client to 3.1.10 or later.

Summary

Eclipse Jersey has a Race Condition

In Eclipse Jersey versions 2.45, 3.0.16, 3.1.9 a race condition can cause ignoring of critical SSL configurations - such as mutual authentication, custom key/trust stores, and other security settings. This issue may result in SSLHandshakeException under normal circumstances, but under certain conditions, it could lead to unauthorized trust in insecure servers (see PoC)

Impact

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

Affected versions

org.glassfish.jersey.core:jersey-client (= 2.45) org.glassfish.jersey.core:jersey-client (= 3.0.16) org.glassfish.jersey.core:jersey-client (= 3.1.9)

Security releases

org.glassfish.jersey.core:jersey-client → 2.46 (maven) org.glassfish.jersey.core:jersey-client → 3.0.17 (maven) org.glassfish.jersey.core:jersey-client → 3.1.10 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.glassfish.jersey.core:jersey-client to 2.46 or later; org.glassfish.jersey.core:jersey-client to 3.0.17 or later; org.glassfish.jersey.core:jersey-client to 3.1.10 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-12383? CVE-2025-12383 is a critical-severity race condition vulnerability in org.glassfish.jersey.core:jersey-client (maven), affecting versions = 2.45. It is fixed in 2.46, 3.0.17, 3.1.10. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
Which versions of org.glassfish.jersey.core:jersey-client are affected by CVE-2025-12383? org.glassfish.jersey.core:jersey-client (maven) versions = 2.45 is affected.
Is there a fix for CVE-2025-12383? Yes. CVE-2025-12383 is fixed in 2.46, 3.0.17, 3.1.10. Upgrade to this version or later.
Is CVE-2025-12383 exploitable, and should I be worried? Whether CVE-2025-12383 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-12383 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-12383?
- Upgrade org.glassfish.jersey.core:jersey-client to 2.46 or later
- Upgrade org.glassfish.jersey.core:jersey-client to 3.0.17 or later
- Upgrade org.glassfish.jersey.core:jersey-client to 3.1.10 or later