Skip to main content
Menu
CVEs

Eclipse Yasson cross-user data exposure in JsonbNumberFormat handling

CVE-2026-132043EUVD-2026-129500GHSA-W4VP-JHX9-25M7Published November 19, 2026, updated

6.3MediumCNA
Exploited
Proof of concept public, per CISA
Fix
No fix listed
Who is exposed
Not reported

Summary

Eclipse Yasson, a Java JSON-binding library, has a race condition in how it handles @JsonbNumberFormat: threads sharing one Jsonb instance can get another caller's number or a wrong value, or fail with an exception. A remote attacker who can send concurrent requests can cause incorrect data to be processed or another user's value to be returned, but only if the application uses this annotation with a shared Jsonb instance and the attacker wins a timing race.

Written by a model

Original 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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-132043 (Concurrent formatted-number parsing can return another caller's value), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-132043 (entry last updated 2026-11-19):
Affected:
- Eclipse Foundation Eclipse Yasson: from 3.0, through 3.0.5
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132043 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132043 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1356
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/603
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-132043
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132043"}.

Affected versions

cve.now Index

43Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.3/10CVSS 6.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 48 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
Linkgitlab.eclipse.org · security/vulnerability-reports/-/work_items/1356
Linkgitlab.eclipse.org · security/cve-assignment/-/work_items/603
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132043
RecordNVD · CVE-2026-132043

Questions about CVE-2026-132043

Is CVE-2026-132043 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-132043?

Eclipse Yasson: from 3.0 through 3.0.5.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.