# CVE-2026-50189: Appsmith: RCE via Supervisord XML-RPC Admin Interface Exposed via /supervisor Caddy Route

> Authenticated administrators can execute OS commands in the container by abusing an exposed Supervisord XML-RPC interface via a reverse proxy route.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** BIT-appsmith-2026-50189, GHSA-v49v-673j-g4vj

## What is CVE-2026-50189?

CVE-2026-50189 is a high-severity server-side request forgery vulnerability in appsmithorg appsmith, published on 24 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Appsmith is a platform to build admin panels, internal tools, and dashboards. Prior to 2.1, Appsmith's bundled supervisord exposes an XML-RPC interface on port 9001, reachable from outside the container via a Caddy reverse-proxy route at /supervisor/* on the public ingress. Combined with the APPSMITH_SUPERVISOR_PASSWORD exposed via GET /api/v1/admin/env, any authenticated administrator can send arbitrary XML-RPC calls to supervisord and execute OS commands inside the Docker container via twiddler.addProgramToGroup. This vulnerability is fixed in 2.1.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-183 (Permissive List of Allowed Inputs)

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

1 open source package ship an affected version, including appsmith. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `appsmith` | Bitnami | All versions | 2.1.0 |

Products: Appsmith Appsmith.

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

Upgrade appsmith to 2.1.0 or later.

## Is CVE-2026-50189 being exploited?

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

## Other vulnerabilities in appsmithorg appsmith

- [CVE-2026-55454](https://insights.sbomify.com/CVE-2026-55454/): Appsmith: Caddy admin API exposed without authentication (critical 9.9)
- [CVE-2024-55964](https://insights.sbomify.com/CVE-2024-55964/): Code injection in n/a (critical 9.8)
- [CVE-2026-22794](https://insights.sbomify.com/CVE-2026-22794/): Account Takeover Vulnerability in Appsmith (critical 9.7)
- [CVE-2026-24042](https://insights.sbomify.com/CVE-2026-24042/): Appsmith public apps can execute unpublished actions (viewMode confusion) (critical 9.4)
- [CVE-2026-30862](https://insights.sbomify.com/CVE-2026-30862/): Critical Stored XSS & Privilege Escalation in Appsmith (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50189 is a high-severity server-side request forgery vulnerability in appsmithorg appsmith, published on 24 Jun 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-50189 exists.

Affected packages and fixed versions:
- appsmith (Bitnami): affected all versions; fixed in 2.1.0

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-50189/ (Markdown: https://insights.sbomify.com/CVE-2026-50189/index.md)
```

## Sources

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

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