Vulnerability in Liman (CVE-2026-57499)
Summary
Vulnerability in Liman (CVE-2026-57499). Successful exploitation can lead to full system takeover. Exploitable via ip_address. Mitigation: upgrade to 2.2.2 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-57499 has been found in Liman.
Attackers can target a specific entry point like ip_address over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: upgrade Liman to 2.2.2 or later.
If unsure, ask your IT team or search "Liman CVE-2026-57499" on the vendor's site.
CVE-2026-57499 (Liman) — CWE-20 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ip_address
Patched: 2.2.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in Liman. Attackers reach the vulnerable code path via ip_address.
Check the vendor advisory for the affected versions of Liman. Attack surface: ip_address.
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover.
Update to 2.2.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Liman' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Liman' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Limanを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Liman to 2.2.2ステージング環境で 2.2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com