Security readout for executives and security teams
Plain-English summary
A logged-in Liman administrator can abuse the log-rotation configuration feature to run operating-system commands on the server. Successful exploitation could expose data, alter the system, or disrupt service. The flaw affects releases before 2.2.2 - 1103 and is fixed in that release.
Executive priority
Treat this as an urgent patching item for affected Liman servers, especially externally reachable management systems. Administrator privileges reduce opportunistic exposure but do not materially reduce impact after credential compromise. Prioritize version confirmation, upgrade, access restriction, and evidence review.
Technical view
The log-rotation endpoint places the `ip_address` parameter directly into a shell command without sanitization. Single-quote injection can escape the intended command context, producing authenticated remote code execution. CVSS 3.1 scores it 9.1 with network access, low complexity, high privileges, no user interaction, and changed scope.
Likely exposure
Exposure is limited to Liman core versions earlier than 2.2.2 - 1103 where an attacker can authenticate as an administrator and reach the vulnerable endpoint. Internet-accessible administration interfaces, excessive administrator access, or compromised administrator credentials increase practical risk. No CPE identifiers were supplied.
Exploitation context
The supplied sources do not establish active exploitation, and CVE-2026-57499 is not identified as a KEV entry in the bundle. Exploitation requires administrator privileges, but success provides operating-system command execution with potentially complete confidentiality, integrity, and availability impact.
Researcher notes
The reported weakness maps to CWE-20 and CWE-78. The injection boundary is the unsanitized `ip_address` value within a shell command. The changed-scope CVSS vector reflects consequences beyond the vulnerable web component. Public evidence supplied here confirms the flaw and fix, but not observed attacks or exploit availability.
Mitigation direction
- Upgrade Liman core to version 2.2.2 - 1103 or later.
- Restrict Liman administration access to trusted networks and authorized administrators.
- Review administrator accounts and revoke unnecessary, stale, or suspicious access.
- Consult the vendor advisory for any additional deployment-specific guidance.
Validation and detection
- Inventory Liman installations and record their exact core versions.
- Confirm every installation runs 2.2.2 - 1103 or later.
- Identify who can authenticate as an administrator and reach log-rotation configuration.
- Review relevant application, proxy, and system logs for anomalous endpoint access or unexpected processes.
- After upgrading, verify normal log-rotation configuration behavior without using malicious inputs.
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-20: 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-78: 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-57499 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
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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.
SSVC decision data
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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/limanmys/core/security/advisories/GHSA-3jrp-54r2-9g63CVE reference, GitHub_M · x_refsource_CONFIRM
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.