Liman is open source server management software. Prior to 2.2.2 - 1103, an OS command injection vulnerability in the log rotation configuration endpoint allows an authenticated administrator to execute arbitrary operating system commands on the Liman server. The ip_address parameter is embedded directly into a shell command without sanitization, enabling shell escape via single-quote injection. This is fixed in 2.2.2 - 1103.
CVE-2026-57499
This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0%, top 42% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(medium)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 58%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 27, 2026
Advisory Details (1)
Auto-updated Aug 29, 2026OS Command Injection in LogRotationController allows authenticated admin to execute arbitrary commands (RCE) · Advisory · limanmys/core · GitHub
https://github.com/limanmys/core/security/advisories/GHSA-3jrp-54r2-9g63Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-30 02:17 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 23:56 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 17:27 UTCEG score recompute
- 2026-08-27 16:48 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20 · CWE-78
Frequently asked(5)
What is CVE-2026-57499?
When was CVE-2026-57499 disclosed?
Is CVE-2026-57499 actively exploited?
What is the CVSS score of CVE-2026-57499?
How do I remediate CVE-2026-57499?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57499
Is Your Infrastructure Affected by CVE-2026-57499?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.