# CVE-2026-5120: Race Condition vulnerability affecting BIOVIA Workbook from Release 2021 through Release 2026

> A race condition in BIOVIA Workbook allows users to access unauthorized data from other users.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-9cqm-4635-4v3j

## What is CVE-2026-5120?

CVE-2026-5120 is a high-severity vulnerability in Dassault Systèmes BIOVIA Workbook, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Race Condition vulnerability affecting BIOVIA Workbook from Release 2021 through Release 2026 could allow a user to access unauthorized data from another user.

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

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


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

No fix has been published for CVE-2026-5120 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5120 being exploited?

There is no known exploitation of CVE-2026-5120 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5120 is a high-severity vulnerability in Dassault Systèmes BIOVIA Workbook, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5120 in the wild and no public exploit code.

Affected product: Dassault Systèmes BIOVIA Workbook. 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-5120/ (Markdown: https://insights.sbomify.com/CVE-2026-5120/index.md)
```

## Sources

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

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