Security readout for executives and security teams
Plain-English summary
CVE-2026-1064 is a command injection issue in Bastillion 4.0.0 and 4.0.1. A remote authenticated attacker may be able to make the server run unintended commands. Public exploit material is referenced, but the sources do not show active exploitation or a vendor patch.
Executive priority
Treat as a near-term remediation and exposure-reduction item for any Bastillion 4.0.0 or 4.0.1 deployment. Prioritize internet-facing or shared administrative environments because public exploit information exists, even though active exploitation is not documented.
Technical view
The issue affects Bastillion’s System Management Module, specifically processing in SystemKtrl.java. VulDB lists CWE-74 and CWE-77, CVSS v2 5.8, AV:N/AC:L/Au:M/C:P/I:P/A:P. The disclosure says exploitation can be remote and proof-of-concept code is public. Vendor response and official remediation are not documented in the provided sources.
Likely exposure
Exposure is likely limited to organizations running Bastillion 4.0.0 or 4.0.1 where authenticated users can reach the Bastillion management interface. Internet-facing or broadly accessible administrative deployments carry higher operational risk.
Exploitation context
Public exploit material is cited, so the vulnerability is more actionable than a purely theoretical bug. However, it is not listed in KEV, and the provided sources do not cite observed active exploitation. Authentication is required according to the CVSS vector.
Researcher notes
Evidence is based on CVE and VulDB records plus a public GitHub report reference. The affected code path is described only at a high level as SystemKtrl.java processing. Vendor confirmation, patch status, and precise vulnerable parameter details are not established in the provided bundle.
Mitigation direction
- Inventory Bastillion deployments and identify versions 4.0.0 and 4.0.1.
- Check Bastillion vendor channels for updated guidance or fixed releases.
- Restrict Bastillion access to trusted administrative networks and users.
- Review Bastillion account privileges and remove unnecessary access.
- Increase monitoring for suspicious administrative activity on Bastillion hosts.
Validation and detection
- Confirm the installed Bastillion version on each deployment.
- Verify whether the management interface is reachable from untrusted networks.
- Review user access lists for accounts able to use management functions.
- Check logs for unusual commands or administrative actions.
- Track vendor, CVE, and VulDB updates for remediation changes.
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-1064 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-341632 | bastillion-io Bastillion System Management SystemKtrl.java command injectionCVE reference · vdb-entry, technical-description
- VDB-341632 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #731308 | bastillion-io Bastillion SSH Key Manager <=4.0.1 Command InjectionCVE reference · third-party-advisory
- https://github.com/AnalogyC0de/public_exp/blob/main/archives/Bastillion/report2.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.