CVE-2026-60112: Nasa Ait Gui authentication bypass (CVSS 9.8)

Description

AMMOS Instrument Toolkit (AIT) GUI before 2.5.1 contains a missing authentication vulnerability that allows any unauthenticated network attacker to obtain a valid session and issue arbitrary spacecraft commands by calling Sessions.create() without any credential check. Attackers can exploit the unauthenticated session issuance in Sessions.create() and subsequently invoke handle_cmd() to forward arbitrary commands directly to the AIT command bus without any authentication gate between session creation and command dispatch.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Nasa Ait Gui< 2.5.1

Remediation

Fixed in

Nasa Ait Gui≥ 2.5.1

Patch & vendor advisories

References

https://github.com/NASA-AMMOS/AIT-GUI/blob/2.5.1/CHANGELOG.mdRelease Notes
https://github.com/NASA-AMMOS/AIT-GUI/commit/beb8fc0813eded89f985d3eb9a73535dd327726dPatch
https://github.com/NASA-AMMOS/AIT-GUI/releases/tag/2.5.1ProductRelease Notes
https://www.vulncheck.com/advisories/ait-gui-missing-authentication-via-sessions-createPatchRelease NotesThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-60112 being actively exploited?

CVE-2026-60112 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.79%.

How severe is CVE-2026-60112?

CVE-2026-60112 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.79% probability of exploitation.

Which products are affected by CVE-2026-60112?

Affected products include Nasa Ait Gui.

How do I fix CVE-2026-60112?

Upgrade affected software to a fixed version, for example Nasa Ait Gui 2.5.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-60112 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo