Authenticated code execution via unchecked post-clone paths
Published Jul 1, 2026 · Updated Jul 1, 2026
Path traversal in the Git Service in Altium Enterprise Server and Altium 365 allows remote authenticated users to execute code. The CloneRepository action accepts post-clone file-move operations and uses user-supplied paths without validating that destinations remain inside the repository area. Basic Git access is sufficient to plant attacker-controlled scripts for execution as the Git Service account, exposing co-resident tenant data in multi-tenant cloud deployments.
Summary
What happened
Path traversal in the Git Service in Altium Enterprise Server and Altium 365 allows remote authenticated users to execute code. The CloneRepository action accepts post-clone file-move operations and uses user-supplied paths without validating that destinations remain inside the repository area. Basic Git access is sufficient to plant attacker-controlled scripts for execution as the Git Service account, exposing co-resident tenant data in multi-tenant cloud deployments.
The record
- CVE
- CVE-2026-14439
- Published
- Jul 1, 2026
- Updated
- Jul 1, 2026
- Vendor
- Altium
- Product
- Altium 365
- Classifications
- CWE-94, CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 1, 2026CVE publishedPublication date reported by the CVE source.
- Jul 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo