CVE-2026-132043
Received Received - Intake

Race Condition in Eclipse Yasson JSON Deserialization

Vulnerability report for CVE-2026-132043, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-19

Last updated on: 2026-11-19

Assigner: Eclipse Foundation

Description

In Eclipse Yasson versions 3.0 to 3.0.5, a race condition (CWE-362) exists in the handling of @JsonbNumberFormat. Yasson creates one java.text.NumberFormat instance per annotated property and shares it across all threads that use the same Jsonb instance. NumberFormat is not thread-safe, and the deserializer called parse() on it without synchronization. When multiple threads deserialize concurrently, a thread can receive a numeric value that belongs to another thread's input, receive an incorrect value, or fail with an exception. A remote attacker who can send concurrent requests to an application that deserializes untrusted JSON this way may cause incorrect data to be processed or cause another user's value to be returned. Exploitation requires that the application use @JsonbNumberFormat with a shared Jsonb instance and that the attacker win a timing race. This issue is fixed in version 3.0.6 by synchronizing access to the shared NumberFormat instances.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-19
Last Modified
2026-11-19
Generated
2026-11-20
AI Q&A
2026-11-19
EPSS Evaluated
2026-11-19
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Eclipse Foundation Eclipse Yasson From 3.0 (inc) to 3.0.5 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a race condition in Eclipse Yasson versions 3.0 to 3.0.5 where a shared non-thread-safe NumberFormat instance is used across threads during JSON deserialization. When multiple threads parse numeric values with @JsonbNumberFormat, incorrect data or exceptions may occur due to unsynchronized access.

Detection Guidance

Detecting this vulnerability requires checking if your Eclipse Yasson version is between 3.0 and 3.0.5 and if your application uses @JsonbNumberFormat with a shared Jsonb instance. Review application logs for parsing exceptions or incorrect numeric values during concurrent JSON deserialization.

Impact Analysis

An attacker could send concurrent requests to an application processing untrusted JSON, causing incorrect numeric values to be processed or another user's data to be exposed. This may lead to data corruption, parsing errors, or unauthorized access to sensitive information.

Compliance Impact

This vulnerability could lead to incorrect data processing or exposure of another user's data during concurrent JSON deserialization. For GDPR, this may violate principles of data accuracy and confidentiality. For HIPAA, it could result in unauthorized access or corruption of protected health information.

Mitigation Strategies

Upgrade Eclipse Yasson to version 3.0.6 or later to apply the synchronization fix. If upgrading is not immediately possible, avoid using @JsonbNumberFormat with shared Jsonb instances or implement custom synchronization around deserialization of annotated fields.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-132043. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...