CVE-2026-11429
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 · uneditedTwo endpoints in the Vault Service ScriptsController, shared by Altium Enterprise Server and Altium 365, accept file uploads where a user-supplied filename component is used to construct the destination path without validation, allowing arbitrary files to be written to any location writable by the service account. Because the file write operation completes before authentication is validated, the vulnerability can be exploited without any credentials, session, or prior knowledge of the system. An unauthenticated network attacker can use this primitive to place executable content in directories where it is later executed by the service, resulting in remote code execution under the Vault Service account. Altium Enterprise Server is fixed in 8.1.1; the issue has been remediated in Altium 365 (commercial and government cloud) at the service level.
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 confidencePre-authentication file upload vulnerability in Vault Service ScriptsController allows unauthenticated attackers to write arbitrary files to any writable location by supplying a path traversal sequence in the filename. The file write completes before authentication validation, enabling placement of executable content in directories where it's later run, achieving RCE under the Vault Service account.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Altium Enterprise Server is installedLook for the Altium Enterprise Server installation directory, typically under C:\Program Files\Altium\Altium Enterprise Server or C:\Program Files (x86)\Altium\Altium Enterprise Server. Check for the Vault service in Windows Services (service name typically contains 'Vault').Affected if Altium Enterprise Server is present on the system
-
Determine Vault Service versionIn Windows Services, locate the Vault service (e.g., 'Altium Vault Service'). Right-click and select Properties, then check the 'Path to executable' to find the install location. Right-click the VaultService.exe file, select Properties, and check the File Version tab.Affected if The installed version is lower than 8.1.1
-
Verify ScriptsController endpoint is exposedCheck if the Vault web service is running and accessible. The vulnerable endpoint is typically at /ScriptsController/upload or similar paths under the Vault web API. Review IIS or embedded web server configuration for the Vault service.Affected if The Vault web interface is accessible over the network without authentication
-
Check file system permissions on service accountReview the service account running the Vault service (from Services > Vault service > Properties > Log On). Use icacls or accessenum tools to check if this account has write permissions to sensitive directories like the web root, startup folders, or system executable directories.Affected if The Vault service account has write access to directories where executable content can be placed and subsequently run
The environment is affected if Altium Enterprise Server with Vault Service is installed and the version is below 8.1.1, with the Vault web service accessible and the service account having write permissions to executable directories.
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.
dbcve · scopedUpgrade Altium Enterprise Server to version 8.1.1 or later. For Altium 365 deployments, verify with Altium that the service-side remediation has been applied.
Altium Enterprise Server 8.1.1 or later
- 1. Identify the current version of Altium Enterprise Server by accessing the Altium Administration panel or checking the installed Vault Service version
- 2. For Altium Enterprise Server: Schedule a maintenance window and upgrade to version 8.1.1 or later, following Altium's standard upgrade procedures
- 3. Verify the upgrade was successful by confirming the Vault Service ScriptsController no longer allows unauthenticated file uploads with arbitrary paths
- 4. For Altium 365: No customer action required; the fix has been applied at the service level by Altium
- 5. After upgrading, verify that the path traversal vulnerability is no longer exploitable by testing file upload endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11429 — 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-11429 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