# CVE-2026-27811: Roxy-WI has a Command Injection via diff parameter in config comparison allows authenticated RCE

> Authenticated attackers can execute arbitrary system commands on the host via a command injection flaw in the configuration comparison feature.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2026
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-jvmv-cw47-jh77

## What is CVE-2026-27811?

CVE-2026-27811 is a high-severity command injection vulnerability in roxy-wi, published on 17 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. Prior to version 8.2.6.3, a command injection vulnerability exists in the `/config/compare/<service>/<server_ip>/show` endpoint, allowed authenticated users to execute arbitrary system commands on the app host. The vulnerability exists in `app/modules/config/config.py` on line 362, where user input is directly formatted in the template string that is eventually executed. Version 8.2.6.3 fixes the issue.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Roxy-Wi Roxy-Wi.

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

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

## Is CVE-2026-27811 being exploited?

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

## Other vulnerabilities in roxy-wi

- [CVE-2022-31161](https://insights.sbomify.com/CVE-2022-31161/): Roxy-WI Vulnerable to Unauthenticated Remote Code Execution via ssl_cert Upload (critical 10.0)
- [CVE-2022-31137](https://insights.sbomify.com/CVE-2022-31137/): Unauthenticated Remote Code Execution in Roxy-WI (critical 10.0)
- [CVE-2022-31125](https://insights.sbomify.com/CVE-2022-31125/): Authentication Bypass in Roxy-wi (critical 10.0)
- [CVE-2022-31126](https://insights.sbomify.com/CVE-2022-31126/): Unauthenticated Remote Code Execution in Roxy-wi (critical 10.0)
- [CVE-2021-38167](https://insights.sbomify.com/CVE-2021-38167/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27811 is a high-severity command injection vulnerability in roxy-wi, published on 17 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27811 exists.

Affected product: roxy-wi. 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-27811/ (Markdown: https://insights.sbomify.com/CVE-2026-27811/index.md)
```

## Sources

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

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