dbcve.org
On Prem Enterprise ServerApplication · Altium

CVE-2026-11414

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 8.1.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A hard-coded cryptographic key is used by Altium Enterprise Server to sign file download URLs in the Vault service. Because the key is identical across all installations, an unauthenticated network attacker who can reach the server can forge valid download signatures and retrieve files from the Vault storage area without any authentication, session, or credentials. A separate path traversal vulnerability in the same download endpoint allows the configured storage root to be escaped, enabling reads of arbitrary files on the server filesystem. Combined, these issues allow an unauthenticated attacker to obtain sensitive server configuration and key material, which can lead to full server compromise. The vulnerability can be chained with CVE-2026-9152 to enumerate and bulk-download stored content. Altium 365 cloud deployments are not impacted in practice, as file storage uses object storage rather than the local filesystem.

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

Hard-coded cryptographic key in Altium Enterprise Server's Vault service allows unauthenticated attackers to forge valid download URL signatures. Combined with a path traversal vulnerability in the same endpoint, attackers can escape the storage root and read arbitrary files on the server filesystem, exposing sensitive configuration and key material leading to full server compromise.

MitigationReplace hard-coded cryptographic keys with securely generated unique keys per installation and implement strict path validation to prevent traversal attacks in the file download endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
On Prem Enterprise ServerApplication
Affected:< 8.1.1

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 and version
    Locate the Altium Enterprise Server installation directory and check the version information, typically found in server configuration files, registry entries, or the server management interface
    Affected if Version is present and less than 8.1.1
  2. Verify the Vault service is enabled
    Check the server configuration to determine if the Vault service component is installed and active
    Affected if Vault service is enabled and version is < 8.1.1
  3. Locate Vault service configuration files
    Search the installation directory for Vault-related configuration files that handle download URL signature generation
    Affected if Configuration files exist and contain hard-coded cryptographic keys instead of installation-specific unique keys
  4. Inspect download endpoint configuration
    Examine the file download endpoint configuration within the Vault service for path validation settings
    Affected if Path traversal protection is missing or inadequate in the download endpoint configuration

Your environment is affected if Altium Enterprise Server version is below 8.1.1, the Vault service is enabled, and the configuration contains hard-coded cryptographic keys used for URL signature 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.

dbcve · scoped
Upgrade available Upgrade to 8.1.1 or later
Fixed in 8.1.1
Interim mitigation

Replace hard-coded cryptographic keys with securely generated unique keys per installation and implement strict path validation to prevent traversal attacks in the file download endpoint.

Recommended fix High confidence

8.1.1

  1. Backup the current Altium Enterprise Server installation and all associated data
  2. Download Altium Enterprise Server version 8.1.1 or later from the official Altium download portal
  3. Review the Altium Enterprise Server upgrade documentation for version 8.1.1
  4. Execute the upgrade process following the documented upgrade procedure
  5. Verify the installation by confirming the Vault service is operational
  6. Test that the download URL signature mechanism is functioning correctly with the new implementation
  7. Validate that the path traversal protection is working by attempting to access files outside the storage root (in a safe, non-production test environment)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in On Prem Enterprise Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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