CVE-2026-132043: In Eclipse Yasson versions 3.0 to 3.0.5, a race condition exists in the handling of
Source GCVE Database
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, 12:38 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– |
Mavenorg.eclipse/yassonpkg:maven/org.eclipse/yassonOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Eclipse Yasson to version 3.0.6 or later, where the issue is fixed by synchronizing access to shared NumberFormat instances. Until upgraded, avoid sharing Jsonb instances with @JsonbNumberFormat annotations across threads or implement external synchronization to prevent concurrent access to NumberFormat instances.
Description
Eclipse Yasson versions 3.0 to 3.0.5 contain a race condition in the handling of @JsonbNumberFormat due to unsafe concurrent use of java.text.NumberFormat instances. This can cause incorrect numeric values to be deserialized or exceptions to occur when multiple threads deserialize JSON concurrently using a shared Jsonb instance. The issue is fixed in version 3.0.6 by synchronizing access to the shared NumberFormat instances.