CVE-2026-11423

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Altium) lists Altium Enterprise Server versions before 8.1.1 as affected. No release containing a fix is confirmed on record.

A path traversal vulnerability exists in the Altium Enterprise Server Collaboration Service due to improper handling of user-supplied filenames in the MCAD and Simulation file download flows. A regular authenticated user can submit a collaboration message containing a crafted filename, which is later used to construct the download path on the server without validation, allowing arbitrary files to be read from the server filesystem.

Because the readable files include the server's master configuration, which stores credentials for privileged accounts, exploitation can lead to authenticating as a system administrator and gaining full control of the server. Altium 365 cloud deployments are not affected.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
The EG Score, 9.4 of 10.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 5, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
No fix on record yet.

Vendor Advisories for CVE-2026-11423(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 17× in last 7d / 31× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 428 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 328 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  2. 2026-10-15 07:05 UTCEG score recompute
  3. 2026-10-15 07:05 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  4. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-10-14 02:56 UTCEG score recompute
  6. 2026-10-14 02:56 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  7. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-10-12 23:03 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  9. 2026-10-12 16:37 UTCEG score recompute
  10. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-10-12 09:51 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  12. 2026-10-11 20:13 UTCEG score recompute
  13. 2026-10-11 18:25 UTCEG score recompute
  14. 2026-10-11 14:59 UTCEG score recompute
  15. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  18. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  19. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  21. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  24. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  25. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
Show 75 more
  1. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  2. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  4. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-09-14 09:24 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  9. 2026-09-14 05:00 UTCEG score recompute
  10. 2026-09-14 05:00 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  11. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  14. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  15. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  16. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  20. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  21. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  26. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  28. 2026-08-25 06:16 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  29. 2026-08-25 01:49 UTCEG score recompute
  30. 2026-08-25 01:49 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  31. 2026-08-23 21:10 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  32. 2026-08-23 16:46 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  33. 2026-08-23 12:22 UTCEG score recompute
  34. 2026-08-23 12:22 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  35. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  36. 2026-08-22 00:30 UTCEG score recompute
  37. 2026-08-22 00:30 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  38. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  39. 2026-08-21 20:06 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  40. 2026-08-21 12:45 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  41. 2026-08-21 06:42 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  42. 2026-08-21 02:15 UTCEG score recompute
  43. 2026-08-21 02:15 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  44. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  45. 2026-08-20 21:50 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  46. 2026-08-20 17:26 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  47. 2026-08-20 09:37 UTCEG score recompute
  48. 2026-08-20 09:37 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  49. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  50. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  51. 2026-08-17 15:36 UTCEG score recompute
  52. 2026-08-17 15:36 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  53. 2026-08-17 11:06 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  54. 2026-08-17 06:40 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  55. 2026-08-17 02:10 UTCEG score recompute
  56. 2026-08-17 02:10 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  57. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-08-16 14:49 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  59. 2026-08-16 10:25 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  60. 2026-08-16 06:02 UTCEG score recompute
  61. 2026-08-16 06:02 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  62. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-08-16 01:39 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  64. 2026-08-15 16:41 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  65. 2026-08-15 12:17 UTCEG score recompute
  66. 2026-08-15 12:17 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  67. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  68. 2026-08-15 00:56 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  69. 2026-08-14 20:32 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  70. 2026-08-14 16:04 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  71. 2026-08-14 11:40 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  72. 2026-08-14 07:17 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  73. 2026-08-14 02:54 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL
  74. 2026-08-13 22:30 UTCEG score recompute
  75. 2026-08-13 22:30 UTCGHSA enrichmentGHSA-8mjc-gx82-2m9v · GitHub severity CRITICAL

Frequently asked(5)

What is CVE-2026-11423?
CVE-2026-11423 is a critical-severity vulnerability; its CVE record was published on June 5, 2026. A path traversal vulnerability exists in the Altium Enterprise Server Collaboration Service due to improper handling of user-supplied filenames in the MCAD and Simulation file download flows. A regular authenticated user can submit a collaboration message containing a crafted filename, which is…
When was CVE-2026-11423 made public?
CVE-2026-11423 was made public on June 5, 2026: that is the date its CVE record's CNA, Altium, gives for when the vulnerability was made public. The CVE record itself was published on June 5, 2026. EchelonGraph's copy of the record carries a last-modified date of July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-11423 actively exploited?
CVE-2026-11423 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11423?
CVE-2026-11423 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11423?
No fix for CVE-2026-11423 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Altium) lists Altium Enterprise Server versions before 8.1.1 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-11423 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-11423?

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