dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-14439

CRITICAL · 9.4 CVSS v4.0 Published 2026-07-01
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 8 weeks old

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 Git Service component shared by Altium Enterprise Server and Altium 365. The service accepts a sequence of post-clone file-manipulation operations that use user-supplied paths without validation, allowing an authenticated user with basic git access to move arbitrary files outside the intended repository area. This file-move primitive can be used to place attacker-controlled script content into directories where it is later executed by the service, resulting in remote code execution under the Git Service account. On multi-tenant Altium 365 deployments, this could have allowed access to data belonging to other tenants on the same infrastructure node. 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 confidence

A path traversal vulnerability in the Git Service component allows authenticated users with basic git access to manipulate file paths without validation during post-clone operations. This enables moving arbitrary files outside the repository area and placing malicious scripts in executable directories, resulting in RCE under the Git Service account and potential cross-tenant data access on multi-tenant deployments.

MitigationUpgrade to Altium Enterprise Server 8.1.1 or later; Altium 365 customers are already protected at the service level.

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 if Git Service component is enabled
    Access Altium Enterprise Server or Altium 365 administration panel and locate the Git Service module status, or query the service configuration via API endpoint /api/git/service/status
    Affected if Git Service is enabled and accessible to authenticated users with basic git access
  2. Determine installed Altium Enterprise Server version
    Log into the server administration interface and navigate to System Information or About section; alternatively, check the installation directory for a version file or run: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Altium\AltiumEnterpriseServer' -Name Version
    Affected if Version is lower than 8.1.1 (e.g., 8.0.x, 7.x, etc.)
  3. Inspect git operation logs for suspicious path patterns
    Locate git service logs (typically in <install_dir>/logs/git/ or via the web UI Logs viewer) and search for entries containing ../ sequences or unusual file move operations outside repository directories
    Affected if Logs contain path traversal patterns like ../ or file operations targeting directories outside the repository root
  4. Audit executable directories for unauthorized scripts
    Examine directories where git hooks or service scripts are stored (commonly <repo_path>/.git/hooks/ or <install_dir>/scripts/) for new or unexpected executable files with recent modification dates
    Affected if Unexpected .exe, .bat, .ps1, or .sh files appear in hook or script directories, especially if created by the Git Service account
  5. For multi-tenant Altium 365, verify tenant isolation
    Check tenant access logs or audit trails to determine if any user account accessed data belonging to a different tenant organization, particularly via git operations
    Affected if Cross-tenant access events exist in audit logs where users accessed repositories outside their assigned tenant

A user is affected if Git Service is enabled, the Altium Enterprise Server version is below 8.1.1, or abnormal path traversal patterns appear in git logs or unauthorized scripts exist in executable directories.

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

Upgrade to Altium Enterprise Server 8.1.1 or later; Altium 365 customers are already protected at the service level.

Recommended fix Moderate confidence

Altium Enterprise Server 8.1.1 or later

  1. For Altium Enterprise Server: Upgrade to version 8.1.1 or later which contains the security fix for this path traversal vulnerability.
  2. For Altium 365: Contact Altium support to confirm your deployment has received the service-level remediation, as shared multi-tenant deployments have been patched at the service level.
  3. Verify the upgrade was successful by confirming the Git Service component is updated and no longer accepts unvalidated path sequences in post-clone file-manipulation operations.
  4. On multi-tenant deployments, confirm tenant isolation is functioning correctly after remediation.
Caveat Review Altium 8.1.1 release notes for any breaking changes before upgrading production systems

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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