CVE-2026-14439

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
9.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 across Altium 365 shared multi-tenant deployments at the service level; remediation is in progress on remaining Altium 365 deployments.

CVSS v3
9.4
EG Score
9.4(medium)
EPSS
44.5%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 2, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-14439(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 58× in last 7d / 58× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 00:55 UTCEG score recompute
  2. 2026-07-07 00:55 UTCGHSA enrichment
  3. 2026-07-06 20:35 UTCEG score recompute
  4. 2026-07-06 20:35 UTCGHSA enrichment
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:15 UTCEG score recompute
  7. 2026-07-06 16:15 UTCGHSA enrichment
  8. 2026-07-06 11:54 UTCEG score recompute
  9. 2026-07-06 11:54 UTCGHSA enrichment
  10. 2026-07-06 07:32 UTCEG score recompute
  11. 2026-07-06 07:32 UTCGHSA enrichment
  12. 2026-07-06 03:14 UTCEG score recompute
  13. 2026-07-06 03:13 UTCGHSA enrichment
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 22:47 UTCEG score recompute
  16. 2026-07-05 22:47 UTCGHSA enrichment
  17. 2026-07-05 18:28 UTCEG score recompute
  18. 2026-07-05 18:28 UTCGHSA enrichment
  19. 2026-07-05 14:09 UTCEG score recompute
  20. 2026-07-05 14:09 UTCGHSA enrichment
  21. 2026-07-05 09:51 UTCEG score recompute
  22. 2026-07-05 09:50 UTCGHSA enrichment
  23. 2026-07-05 05:31 UTCEG score recompute
  24. 2026-07-05 05:31 UTCGHSA enrichment
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 33 more
  1. 2026-07-05 02:30 UTCEPSS rescore
  2. 2026-07-05 01:12 UTCEG score recompute
  3. 2026-07-05 01:12 UTCGHSA enrichment
  4. 2026-07-04 20:47 UTCEG score recompute
  5. 2026-07-04 20:47 UTCGHSA enrichment
  6. 2026-07-04 16:29 UTCEG score recompute
  7. 2026-07-04 16:29 UTCGHSA enrichment
  8. 2026-07-04 12:09 UTCEG score recompute
  9. 2026-07-04 12:09 UTCGHSA enrichment
  10. 2026-07-04 07:48 UTCEG score recompute
  11. 2026-07-04 07:48 UTCGHSA enrichment
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 03:30 UTCEG score recompute
  14. 2026-07-04 03:29 UTCGHSA enrichment
  15. 2026-07-03 23:11 UTCEG score recompute
  16. 2026-07-03 23:10 UTCGHSA enrichment
  17. 2026-07-03 18:52 UTCEG score recompute
  18. 2026-07-03 18:51 UTCGHSA enrichment
  19. 2026-07-03 14:33 UTCEG score recompute
  20. 2026-07-03 14:33 UTCGHSA enrichment
  21. 2026-07-03 10:14 UTCEG score recompute
  22. 2026-07-03 10:14 UTCGHSA enrichment
  23. 2026-07-03 05:56 UTCEG score recompute
  24. 2026-07-03 05:55 UTCGHSA enrichment
  25. 2026-07-03 01:37 UTCEG score recompute
  26. 2026-07-03 01:36 UTCGHSA enrichment
  27. 2026-07-02 21:18 UTCEG score recompute
  28. 2026-07-02 21:17 UTCGHSA enrichment
  29. 2026-07-02 16:59 UTCEG score recompute 9.40
  30. 2026-07-02 16:59 UTCGHSA enrichment
  31. 2026-07-02 16:58 UTCNVD updateCVSS v3 → 9.4 · CVSS v4 → 9.4
  32. 2026-07-02 01:18 UTCEG score recompute
  33. 2026-07-02 01:18 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-14439?
CVE-2026-14439 is a critical vulnerability published on July 2, 2026. 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…
When was CVE-2026-14439 disclosed?
CVE-2026-14439 was first published in the National Vulnerability Database on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14439 actively exploited?
CVE-2026-14439 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-14439?
CVE-2026-14439 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-14439?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14439, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14439

Explore →

Is Your Infrastructure Affected by CVE-2026-14439?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.