# Eclipse Jersey has a Race Condition Advisory record · `GHSA-7p63-w6x9-6gr7` - **Identifiers:** `GHSA-7p63-w6x9-6gr7` · `CVE-2025-12383` - **State:** Confirmed - **Severity:** CVSS 9.4 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-296](https://cwe.mitre.org/data/definitions/296.html) · [CWE-362](https://cwe.mitre.org/data/definitions/362.html) - **Tags:** [Race condition](https://agentprime.io/advisories/tag/race-condition.md) · [CWE-296](https://agentprime.io/advisories/tag/cwe-296.md) - **Published:** 18 Nov 2025 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 18 Nov 2025, 18:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.4: 9.0 or more. How we decide what’s critical: ## Affected packages - `org.glassfish.jersey.core:jersey-client` (Maven): affected `>=2.45, <2.46 || >=3.0.16, <3.0.17 || >=3.1.9, <3.1.10`; fixed in `2.46`, `3.0.17`, `3.1.10` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Eclipse Jersey's jersey-client (Maven org.glassfish.jersey.core:jersey-client) versions 2.45, 3.0.16 and 3.1.9 are affected by a race condition that can cause critical SSL configurations, such as mutual authentication and custom key or trust stores, to be ignored. Under certain conditions this could let a client trust an insecure server; the source gives few details on how an attacker would trigger it. Upgrade to jersey-client 2.46, 3.0.17 or 3.1.10, matching your version line. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.4 Critical, CVSS 4.0: `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`, from CNA (eclipse) - **CISA KEV:** Not listed. - **EPSS:** 0.0030, the 22nd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:17 UTC: First seen by agentprime - 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7p63-w6x9-6gr7) ## Sources - [GitHub Advisory Database: GHSA-7p63-w6x9-6gr7](https://github.com/advisories/GHSA-7p63-w6x9-6gr7) - [OSV: GHSA-7p63-w6x9-6gr7](https://osv.dev/vulnerability/GHSA-7p63-w6x9-6gr7) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .