CVE-2025-12383: Eclipse Jersey has a Race Condition

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.3%, percentile 21: FIRST’s model estimates a 0.3% chance of exploitation activity in the next 30 days, higher than 21% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes org.glassfish.jersey.core:jersey-client (Maven) = 2.45, fixed in 2.46; org.glassfish.jersey.core:jersey-client (Maven) = 3.0.16, fixed in 3.0.17; org.glassfish.jersey.core:jersey-client (Maven) = 3.1.9, fixed in 3.1.10. Check your lockfile, including transitive dependencies.

What it is

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)

From the GitHub advisory

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)

Weakness type: CWE-362, CWE-296.

Product: org.glassfish.jersey.core:jersey-client (Maven) · Assigned by: eclipse · Published: 2025-11-18

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: high (needs special conditions)
• Attack requirements: present (depends on deployment conditions)
• Privileges required: none (no login)
• User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable no, technical impact partial.
• FIRST EPSS (model of 2026-10-21): 0.30% probability of exploitation activity in the next 30 days; percentile 21.

Timeline

• 2025-11-18 — CVE record last updated
• 2025-11-18 — CVE record published by eclipse
• 2025-11-18 — GitHub-reviewed advisory GHSA-7p63-w6x9-6gr7 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-7p63-w6x9-6gr7 github.com
2. CVE.org record CVE-2025-12383 cve.org
3. NVD entry CVE-2025-12383 nvd.nist.gov

Other references from the CVE record and advisory

1. gitlab.eclipse.org gitlab.eclipse.org
2. github.com github.com
3. github.com github.com
4. github.com github.com
5. github.com github.com
6. github.com github.com
7. github.com github.com
8. github.com github.com
9. gitlab.eclipse.org gitlab.eclipse.org
10. github.com github.com
11. github.com github.com

Critical Maven advisories · Today’s Security Digest