How severe is GHSA-7p63-w6x9-6gr7?

No CVSS score has been assigned to GHSA-7p63-w6x9-6gr7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7p63-w6x9-6gr7?

GHSA-7p63-w6x9-6gr7 affects the following packages: org.glassfish.jersey.core:jersey-client (Maven), org.glassfish.jersey.core:jersey-client (Maven), org.glassfish.jersey.core:jersey-client (Maven). Ecosystems affected: Maven.

How do I fix GHSA-7p63-w6x9-6gr7?

Update org.glassfish.jersey.core:jersey-client to 2.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7p63-w6x9-6gr7 is resolved across your whole dependency graph.

How do I detect GHSA-7p63-w6x9-6gr7 in my Maven dependencies?

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

How do I mitigate GHSA-7p63-w6x9-6gr7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-7p63-w6x9-6gr7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7p63-w6x9-6gr7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-7p63-w6x9-6gr7?

GHSA-7p63-w6x9-6gr7 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th 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 GHSA-7p63-w6x9-6gr7?

GHSA-7p63-w6x9-6gr7 is classified as CWE-362 (CWE-362). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7p63-w6x9-6gr7 published, and has it been updated?

GHSA-7p63-w6x9-6gr7 was published on November 18, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Eclipse Jersey has a Race Condition

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7p63-w6x9-6gr7.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.glassfish.jersey.core:jersey-client☕org.glassfish.jersey.core:jersey-client☕org.glassfish.jersey.core:jersey-client

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 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)

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.glassfish.jersey.core:jersey-client`	≥ 2.45&&< 2.46	2.46`org.glassfish.jersey.core:jersey-client:2.46`
☕Maven	`org.glassfish.jersey.core:jersey-client`	≥ 3.0.16&&< 3.0.17	3.0.17`org.glassfish.jersey.core:jersey-client:3.0.17`
☕Maven	`org.glassfish.jersey.core:jersey-client`	≥ 3.1.9&&< 3.1.10	3.1.10`org.glassfish.jersey.core:jersey-client:3.1.10`

Affected Products

1 product · 3 configurations

Application

jerseyeclipse

3 versions

2.453.0.163.1.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.glassfish.jersey.core:jersey-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.glassfish.jersey.core:jersey-client to 2.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7p63-w6x9-6gr7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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)

O3 Security · Impact-Aware SCA

Is GHSA-7p63-w6x9-6gr7 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Eclipse Jersey has a Race ConditionGHSA-7p63-w6x9-6gr7