CVE-2026-132043: Eclipse Yasson · Race Condition
Affects Eclipse YassonSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium · fixed in 3.0.6 : update Eclipse Yasson when convenient.
Data as of 19 Nov 2026, 09:24 UTC
Thin evidence
One scorer or none| CNA (eclipse) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 3.0.6
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 18 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Eclipse FoundationEclipse Yasson | Affected
| Fixed in– |
AI-suggested
Upgrade to Eclipse Yasson version 3.0.6 or later, where the issue is fixed by synchronizing access to shared NumberFormat instances. No other mitigation is indicated or required.
Description
Eclipse Yasson versions 3.0 through 3.0.5 contain a race condition in the handling of @JsonbNumberFormat due to unsafe sharing of java.text.NumberFormat instances across threads. This can cause incorrect numeric values to be deserialized or exceptions to occur when multiple threads deserialize concurrently. The issue is fixed in version 3.0.6 by synchronizing access to these shared instances.