CVE-2026-105105

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-03. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-92014 (ENISA EUVD) · GHSA-9xfm-37f4-2h8g (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 9.8Exploit: None knownExposed services: Not assessed

Upgrade to AIT-Core 3.1.2 or later (from the CVE record's solution, Turan Security) — apply it.

CWE-306: Missing Authentication for Critical Function in the ait.core.server telemetry and command broker (ait-server) in NASA-AMMOS AIT-Core through 3.1.1 allows an unauthenticated remote attacker with network access to the ZeroMQ message bus to inject spacecraft command data, exfiltrate command and telemetry traffic, inject forged telemetry, or disrupt the command and telemetry bus. The ait-server ZeroMQ broker binds its XSUB and XPUB sockets to all network interfaces by default without authentication or transport security. An attacker able to reach TCP port 5559 can publish messages onto internal topics, including the __commands__ command topic. With the shipped default configuration, command messages are forwarded through command_stream and emitted on the command-uplink UDP path. An attacker able to reach TCP port 5560 can subscribe to command and telemetry traffic on the ground bus. AIT-Core 3.1.2 changes the default ZeroMQ bind addresses to loopback.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: Upgrade to AIT-Core 3.1.2 or later (from the CVE record's solution, Turan Security). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

Upgrade to AIT-Core 3.1.2 or later (from the CVE record's solution, Turan Security). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

October 3, 2026

Last Modified

October 6, 2026

Advisory Details (5)

Auto-updated Oct 31, 2026
Fix named in the CVE record's solution (Turan Security). Sources: github.
GitHub advisoryMentions a patch (unverified)

CWE-306: Missing Authentication for Critical Function in... · CVE-2026-105105 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-9xfm-37f4-2h8g
GitHub advisoryMentions a patch (unverified)

Unauthenticated ZeroMQ command/telemetry bus in AIT-Core allows remote spacecraft command injection and telemetry exfiltration · Advisory · NASA-AMMOS/AIT-Core · GitHub

https://github.com/NASA-AMMOS/AIT-Core/security/advisories/GHSA-ccw5-g774-3683
Web page

GitHub - NASA-AMMOS/AIT-Core · GitHub

https://github.com/NASA-AMMOS/AIT-Core/
Web page

Mothra-1 (Shukrulloh Raximov (Mothra)) · GitHub

https://github.com/Mothra-1
GitHub advisoryMentions a patch (unverified)

AMMOS Instrument Toolkit (AIT) GUI before 2.5.1 contains... · CVE-2026-60112 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-3j6g-pxmx-58qg

Vendor Advisories for CVE-2026-105105(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 137× 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 145 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 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-105105?
CVE-2026-105105 is a critical-severity vulnerability; its CVE record was published on October 3, 2026. CWE-306: Missing Authentication for Critical Function in the ait.core.server telemetry and command broker (ait-server) in NASA-AMMOS AIT-Core through 3.1.1 allows an unauthenticated remote attacker with network access to the ZeroMQ message bus to inject spacecraft command data, exfiltrate command…
When was the CVE record for CVE-2026-105105 published?
The CVE record for CVE-2026-105105 was published on October 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-105105 actively exploited?
CVE-2026-105105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105105?
CVE-2026-105105 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105105?
The CVE record's solution for CVE-2026-105105, written by its CNA Turan Security, names the fix: "Upgrade to AIT-Core 3.1.2 or later." The vendor advisories EchelonGraph has for CVE-2026-105105 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105105?

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