dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-11423

CRITICAL · 9.4 CVSS v4.0 Published 2026-06-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
A path traversal vulnerability exists in the Altium Enterprise Server Collaboration Service due to improper handling of user-supplied filenames in the MCAD and Simulation file download flows. A regular authenticated user can submit a collaboration message containing a crafted filename, which is later used to construct the download path on the server without validation, allowing arbitrary files to be read from the server filesystem. Because the readable files include the server's master configuration, which stores credentials for privileged accounts, exploitation can lead to authenticating as a system administrator and gaining full control of the server. Altium 365 cloud deployments are not affected.

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

Altium Enterprise Server's Collaboration Service contains a path traversal vulnerability in the MCAD and Simulation file download flows. An authenticated user can include a crafted filename in a collaboration message that is used without validation to construct the file path, allowing arbitrary file reads from the server filesystem. The vulnerability is critical because the server's master configuration file containing privileged account credentials can be extracted, enabling the attacker to authenticate as a system administrator and achieve full server control.

MitigationImplement strict input validation and path sanitization on user-supplied filenames in the download flows to prevent path traversal sequences (e.g., ../). Apply the vendor patch for Altium Enterprise Server when available, as the fix requires code changes to the collaboration service.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify Altium Enterprise Server installation
    Locate the Altium Enterprise Server installation directory, typically found in Program Files or a custom install path. Look for the 'CollaborationService' folder or executable.
    Affected if The server is installed and the Collaboration Service component is present.
  2. Determine Collaboration Service version
    Check the version of the Collaboration Service executable or check the assembly/version information in the installation directory.
    Affected if The installed version has not been patched and falls within the vulnerable version range.
  3. Verify Collaboration Service is running
    Check Windows Services or process list for the Altium Collaboration Service process. If using Linux, check for the collaboration service process.
    Affected if The Collaboration Service is actively running and accessible to authenticated users.
  4. Confirm authenticated user access to collaboration messaging
    Verify that standard authenticated users can access the collaboration messaging or file sharing features in Altium Enterprise Server.
    Affected if Authenticated users have access to collaboration features that accept file-related input.
  5. Inspect server configuration files for exposure
    Locate and review configuration files in the Altium Enterprise Server data directories, particularly any files that may contain database credentials, API keys, or administrative account credentials.
    Affected if Sensitive credential files exist in accessible locations on the server filesystem.

A defender is affected if Altium Enterprise Server with an unpatched Collaboration Service is running and authenticated users can access collaboration messaging features that accept file input without strict path validation.

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

Implement strict input validation and path sanitization on user-supplied filenames in the download flows to prevent path traversal sequences (e.g., ../). Apply the vendor patch for Altium Enterprise Server when available, as the fix requires code changes to the collaboration service.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11423 — 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-11423 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