dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-6903

HIGH · 7.5 CVSS v3.1 Published 2026-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The LabOne Web Server, backing the LabOne User Interface, contains insufficient input validation in its file access functionality. An unauthenticated attacker could exploit this vulnerability to read arbitrary files on the host system that are accessible to the operating system user running the LabOne software. Additionally, the Web Server does not sufficiently restrict cross-origin requests, which could allow a remote attacker to trigger file access from a victim's browser by directing the victim to a malicious website. The vulnerability is only exploitable when the LabOne Web Server is running. Installations using only the LabOne APIs without starting the Web Server are not exposed.

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 · high confidence

This is a path traversal vulnerability combined with a CORS misconfiguration in LabOne Web Server. An unauthenticated attacker can read arbitrary files on the host filesystem by exploiting insufficient input validation in the file access functionality. Additionally, the improper CORS policy allows malicious websites to trigger file reads through victim browsers via cross-origin requests.

MitigationApply vendor patches for LabOne Web Server when available; if the web UI is not required, disable the LabOne Web Server and use only the API mode. Network restrict access to the web interface and review CORS policies.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm LabOne Web Server is running
    Check running processes or services for LabOne Web Server (e.g., tasklist on Windows, ps on Linux, or check services.msc). Look for process names containing 'LabOne' or 'webserver'.
    Affected if LabOne Web Server process is active and accepting connections
  2. Identify the installed LabOne Web Server version
    Check the web server version via the web UI footer, check file version properties of the executable, or examine version information in configuration files or release notes shipped with the software.
    Affected if The installed version matches the vulnerable version range (compare your version against any patched versions released by the vendor)
  3. Verify if file access functionality is enabled
    Inspect LabOne Web Server configuration files (typically in the installation directory or conf/ folder) for settings related to file serving, file download, or file access endpoints. Look for parameters that enable or expose file access features.
    Affected if File access functionality is enabled and accessible without authentication
  4. Review CORS policy configuration
    Examine the LabOne Web Server configuration files for CORS-related settings. Look for 'Access-Control-Allow-Origin' directives. Check if the policy accepts wildcard (*) or arbitrary origins without validation.
    Affected if CORS policy allows wildcard origins or does not properly validate the Origin header, enabling cross-origin file read requests
  5. Determine network exposure of the web interface
    Check network listener configuration (e.g., netstat, firewall rules) to determine if the LabOne Web Server is bound to all interfaces (0.0.0.0) or accessible from untrusted networks rather than localhost only.
    Affected if The web interface is exposed to unauthenticated or untrusted network segments

A user is affected if LabOne Web Server is running with file access functionality enabled and a vulnerable CORS configuration, and the installed version falls within the vulnerable range.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for LabOne Web Server when available; if the web UI is not required, disable the LabOne Web Server and use only the API mode. Network restrict access to the web interface and review CORS policies.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6903 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6903 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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