# CVE-2025-12383: Race Condition allows Bypass of Trust Restrictions

> A race condition in Eclipse Jersey allows bypassing SSL trust restrictions, potentially leading to unauthorized trust in insecure servers.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Nov 2025
- **Updated:** 18 Nov 2025
- **Also known as:** CLEANSTART-2026-EJ36501, CLEANSTART-2026-PX86604, CLEANSTART-2026-UT11406, ECHO-e2b4-dac2-0e24, GHSA-7p63-w6x9-6gr7, MINI-234w-cpv6-jj88, MINI-24c8-fpxv-ghhj, MINI-285r-4h55-2qm5, MINI-2mrj-fgp3-qr9r, MINI-4766-h4jx-p6r8, MINI-558c-84h7-rrw4, MINI-575q-qfj3-fg66, MINI-5qxx-vrgh-9vqj, MINI-647q-chj4-cxr9, MINI-68r6-vj9m-3gjv, MINI-phc6-74qv-2757, MINI-vjwv-59xv-hchm, MINI-w4cw-7m9h-2cj4, MINI-xv8w-89xg-rxcp

## What is CVE-2025-12383?

CVE-2025-12383 is a critical vulnerability in Eclipse Foundation Jersey, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2025-12383?

6 open source packages ship an affected version, including org.glassfish.jersey.core:jersey-client. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.glassfish.jersey.core:jersey-client` | Maven | From 2.45 | 2.46 |
| `org.glassfish.jersey.core:jersey-client` | Maven | From 2.45 | 2.46 |
| `org.glassfish.jersey.core:jersey-client` | Maven | From 3.0.16 | 3.0.17 |
| `org.glassfish.jersey.core:jersey-client` | Maven | From 3.0.16 | 3.0.17 |
| `org.glassfish.jersey.core:jersey-client` | Maven | From 3.1.9 | 3.1.10 |
| `org.glassfish.jersey.core:jersey-client` | Maven | From 3.1.9 | 3.1.10 |

Products: Eclipse Jersey.

## How do I fix CVE-2025-12383?

Upgrade org.glassfish.jersey.core:jersey-client to a fixed version for your release line: 2.46, 3.0.17 or 3.1.10.

## Is CVE-2025-12383 being exploited?

There is no known exploitation of CVE-2025-12383 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Foundation Jersey

- [CVE-2021-28168](https://insights.sbomify.com/CVE-2021-28168/): Local information disclosure via system temporary directory (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12383 and fix it if it is affected.

What it is: CVE-2025-12383 is a critical vulnerability in Eclipse Foundation Jersey, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12383 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.glassfish.jersey.core:jersey-client (Maven): affected from 2.45; fixed in 2.46
- org.glassfish.jersey.core:jersey-client (Maven): affected from 2.45; fixed in 2.46
- org.glassfish.jersey.core:jersey-client (Maven): affected from 3.0.16; fixed in 3.0.17
- org.glassfish.jersey.core:jersey-client (Maven): affected from 3.0.16; fixed in 3.0.17
- org.glassfish.jersey.core:jersey-client (Maven): affected from 3.1.9; fixed in 3.1.10
- org.glassfish.jersey.core:jersey-client (Maven): affected from 3.1.9; fixed in 3.1.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12383/ (Markdown: https://insights.sbomify.com/CVE-2025-12383/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12383
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12383
- OSV: https://osv.dev/vulnerability/CVE-2025-12383

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12383/
Summaries are generated and may contain mistakes; the official description above is the record.