Skip to main content
CVE-2025-12383VulnerabilityPublished

CVE-2025-12383: Eclipse Foundation Jersey · Race Condition

Affects Eclipse Foundation JerseySource CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.glassfish.jersey.core/jersey-commonpkg:maven/org.glassfish.jersey.core/jersey-commonOther threatsAffected
  • =2.45
  • =3.0.16
  • =3.1.9
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade Jersey to a patched version once released by the Eclipse Foundation; monitor official channels for updates. 2. Until patches are available, implement external SSL/TLS validation layers such as reverse proxies or API gateways that enforce strict certificate validation and mutual TLS. 3. Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) configured to detect anomalous SSL/TLS handshake behaviors. 4. Conduct thorough code reviews and testing of SSL configuration handling in applications using Jersey to identify potential race conditions. 5. Use static and dynamic analysis tools to detect concurrency issues in SSL-related code paths. 6. Enforce strict network segmentation and monitoring to detect man-in-the-middle attempts. 7. Educate development teams about concurrency risks in security-critical code. 8. Prepare incident response plans specifically addressing SSL/TLS trust failures. These steps go beyond generic advice by focusing on layered defenses and proactive detection until official patches are deployed.

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)

References

Community reviews

Loading reviews…