# CVE-2026-57499: Liman: OS Command Injection in LogRotationController allows authenticated admin to execute arbitrary commands (RCE)

> An authenticated administrator can execute arbitrary OS commands on the Liman server via unsanitized input in the log rotation configuration.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026

## What is CVE-2026-57499?

CVE-2026-57499 is a critical command injection vulnerability in limanmys core, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-57499?


## How do I fix CVE-2026-57499?

No fix has been published for CVE-2026-57499 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-57499 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57499 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57499 and fix it if it is affected.

What it is: CVE-2026-57499 is a critical command injection vulnerability in limanmys core, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57499 exists.

Affected product: limanmys core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57499/ (Markdown: https://insights.sbomify.com/CVE-2026-57499/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57499
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57499
- OSV: https://osv.dev/vulnerability/CVE-2026-57499

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57499/
Summaries are generated and may contain mistakes; the official description above is the record.