Security readout for executives and security teams
Plain-English summary
CVE-2026-1063 is a command injection issue in Bastillion’s public key management component. A logged-in attacker may be able to run unintended system commands through affected Bastillion versions. The issue matters because Bastillion manages SSH access, so compromise could affect administrative control paths. Public exploit material exists, but the sources do not show confirmed active exploitation.
Executive priority
Treat as a near-term security task for any organization using affected Bastillion versions. It is not confirmed as actively exploited, but public exploit disclosure and Bastillion’s role in SSH access management make exposure review and access restriction important.
Technical view
The CVE affects bastillion-io Bastillion 4.0.0 and 4.0.1, specifically AuthKeysKtrl.java in the Public Key Management System. VulDB classifies it as CWE-74/CWE-77 command injection with CVSSv2 5.8: network reachable, low complexity, authentication required, and partial confidentiality, integrity, and availability impact. No fixed version is named in the provided sources.
Likely exposure
Organizations running Bastillion 4.0.0 or 4.0.1 are potentially exposed, especially where the Bastillion web interface is reachable by many users or from untrusted networks. Exposure appears to require authentication based on the CVSS vector and VulDB CTI reference.
Exploitation context
Public exploit information has been disclosed, and VulDB states it may be used. However, the CVE is not marked KEV in the provided bundle, and no cited source confirms active exploitation in the wild. Authentication is required, reducing broad unauthenticated internet risk but not insider or stolen-credential risk.
Researcher notes
Evidence is limited to the CVE/VulDB record and linked public report. The sources identify the affected component and versions but do not name a patch, fixed commit, or vendor advisory. Avoid assuming broader version impact beyond Bastillion 4.0.0 and 4.0.1 unless later vendor evidence confirms it.
Mitigation direction
- Identify all Bastillion deployments and versions immediately.
- If running 4.0.0 or 4.0.1, check vendor/project guidance for updates.
- Restrict Bastillion access to trusted administrative networks.
- Limit Bastillion accounts to necessary administrators only.
- Monitor Bastillion and host logs for suspicious key-management activity.
- Consider compensating controls until a vendor fix is confirmed.
Validation and detection
- Confirm whether Bastillion 4.0.0 or 4.0.1 is installed.
- Verify whether Bastillion is reachable from untrusted networks.
- Review who can authenticate to Bastillion administrative functions.
- Check logs for unusual public key management changes.
- Track CVE and VulDB references for fixed-version updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1063 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.8 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR6.46.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
5.8MediumVector: AV:N/AC:L/Au:M/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341631 | bastillion-io Bastillion Public Key Management System AuthKeysKtrl.java command injectionCVE reference · vdb-entry, technical-description
- VDB-341631 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #731303 | bastillion-io Bastillion <=4.0.1 Command InjectionCVE reference · third-party-advisory
- https://github.com/AnalogyC0de/public_exp/blob/main/archives/Bastillion/report1.mdCVE reference · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.