Quick answers
- Is CVE-2026-50189 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50189 being exploited in the wild.
- How severe is CVE-2026-50189?
- Informational severity, with a CVSS score of 8.9, published 24 June 2026.
- Which products and versions are affected?
- Appsmith < 2.1.
- Is there a fix for CVE-2026-50189?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-50189 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-50189?
- Check whether you run Appsmith at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Appsmith versions prior to 2.1 contain a remote code execution vulnerability due to the exposure of the bundled supervisord XML-RPC interface. The interface, which runs on port 9001, is accessible from outside the container via a Caddy reverse-proxy route at /supervisor/*. An authenticated administrator can retrieve the required 'APPSMITH_SUPERVISOR_PASSWORD' from the /api/v1/admin/env endpoint. By sending a crafted XML-RPC call to the 'twiddler.addProgramToGroup' method, an attacker can register and execute arbitrary shell commands as the 'appsmith' user within the container. This issue is resolved in version 2.1.
Affected products
- Appsmith Appsmith < 2.1
Timeline
- 2026-06-12: advisory: GitHub security advisory published by Appsmith
- 2026-06-24: disclosed: CVE-2026-50189 published to NVD