How severe is CVE-2026-50189?

CVE-2026-50189 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2026-50189?

Affected package information for CVE-2026-50189 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2026-50189?

Apply the appsmith appsmith security patch or hotfix for CVE-2026-50189 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2026-50189 across my infrastructure?

Inventory every appsmith appsmith deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2026-50189 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2026-50189?

O3 detects and blocks CVE-2026-50189 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2026-50189 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-50189 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2026-50189?

CVE-2026-50189 is classified as CWE-183 (CWE-183), Server-Side Request Forgery (SSRF) (CWE-918). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2026-50189?

CVE-2026-50189 affects appsmith appsmith. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-50189 published, and has it been updated?

CVE-2026-50189 was published on June 24, 2026 and was last updated on June 26, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2026-50189: Appsmith CWE-183 (High 7.2)

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.

Affected Products

1 product · 1 configurations

Application

appsmithappsmith

< 2.1

range

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every appsmith appsmith deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the appsmith appsmith security patch or hotfix for CVE-2026-50189 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2026-50189 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2026-50189. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Runtime Protection

Is CVE-2026-50189 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2026-50189 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2026-50189

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2026-50189 being exploited in your environment?