CVE-2026-5120
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Race Condition vulnerability affecting BIOVIA Workbook from Release 2021 through Release 2026 could allow a user to access unauthorized data from another user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA race condition vulnerability in BIOVIA Workbook allows one user to access unauthorized data from another user's session. This timing-based flaw in the multi-user data handling between Release 2021-2026 allows session data to be improperly shared or accessed across concurrent user operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed BIOVIA Workbook versionLocate the application version through the software's About dialog, installation directory metadata, or system registry (common paths include HKEY_LOCAL_MACHINE\SOFTWARE\Dassault Systemes\BIOVIA or HKEY_CURRENT_USER\SOFTWARE\BIOVIA). Compare the version number to the affected range of Release 2021 through Release 2026.Affected if The installed version falls within Release 2021 to Release 2026 inclusive.
-
Confirm multi-user or concurrent session capabilityCheck whether the workbook deployment is configured for multi-user access. This may be indicated by: terminal services/multiple remote desktop sessions enabled, a network deployment with shared workbooks, or a session manager configuration allowing concurrent user connections.Affected if The system is configured to allow multiple users to access workbook sessions simultaneously.
-
Audit active session activityReview server or workstation logs for concurrent session establishment. Check session management utilities, terminal services logs, or application session tracking for evidence of overlapping user sessions accessing the same workbook data.Affected if Multiple concurrent user sessions have been observed accessing the system.
-
Inspect session isolation configurationExamine the workbook or application configuration files for session isolation settings. Look for parameters controlling session data separation, timing windows, or data sharing between concurrent operations.Affected if Session isolation is disabled or misconfigured, allowing improper data sharing between sessions.
You are affected if BIOVIA Workbook Release 2021-2026 is installed AND the system supports or has active concurrent user sessions where session data could be improperly shared.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor patch or upgrade to a version beyond Release 2026 once available. Until then, limit concurrent access to sensitive data and monitor for unauthorized data access attempts.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5120 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5120 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data