# CVE-2026-132043: Concurrent formatted-number parsing can return another caller's value


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-w4vp-jhx9-25m7

## What is CVE-2026-132043?

CVE-2026-132043 is a medium-severity vulnerability in Eclipse Yasson, published on 19 Nov 2026. 

### Official 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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-132043?


## How do I fix CVE-2026-132043?

Upgrade Eclipse Yasson to 3.0.6 or later. The advisory says that version fixes it.

## Is CVE-2026-132043 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132043 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132043 and fix it if it is affected.

What it is: CVE-2026-132043 is a medium-severity vulnerability in Eclipse Yasson, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132043 exists.

Affected product: Eclipse Yasson. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-132043/ (Markdown: https://insights.sbomify.com/CVE-2026-132043/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-132043
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-132043
- OSV: https://osv.dev/vulnerability/CVE-2026-132043

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-132043/
Summaries are generated and may contain mistakes; the official description above is the record.
