CVE-2026-55454

Appsmith: Caddy admin API exposed without authentication

Published Jun 24, 2026 CVSS 3.1 · 9.9 Critical EPSS < 1% KEV · Not listed
Description
Appsmith is a platform to build admin panels, internal tools, and dashboards. Prior to 2.1, the bundled Caddy reverse-proxy's admin API — which has no authentication by default — is bound on 0.0.0.0:2019 inside the container. While this listener is not directly published to the host by docker-compose.yml, it is reachable from the Appsmith server process itself or a SSRF vulnerability. An authenticated low-privileged user can therefore drive the SSRF to issue POST /load (or any other admin-API call) against http://0.0.0.0:2019/, fully replacing the live Caddy configuration and taking over the reverse proxy. This vulnerability is fixed in 2.1.

Analysis

AI-generated

Technical impact

Appsmith versions prior to 2.1 expose a Caddy reverse‑proxy admin API that is bound to 0.0.0.0:2019 inside the container and has no authentication by default. An authenticated user with low privileges can exploit a Server‑Side Request Forgery or the local Appsmith process to send POST /load or any other admin‑API call to http://0.0.0.0:2019/, fully replacing the running Caddy configuration. This allows an attacker to reconfigure or take over the reverse proxy, potentially redirecting, intercepting, or directing traffic to malicious services, effectively enabling remote code execution or privilege escalation.

Affected Systems

All Appsmith deployments using appsmithorg version older than 2.1 are impacted, whether running with default docker‑compose or similar setups. The specific vulnerability is contained within the bundled Caddy reverse‑proxy component bundled with Appsmith.

Risk and Exploitability

The flaw carries a CVSS score of 9.9, indicating critical severity. The EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog. However, the presence of an unauthenticated admin interface and the requirement of only a low‑privileged authenticated user make exploitation straightforward once an SSRF or local execution context is established. The attack vector is likely local to the Appsmith server process or via SSRF, and requires an authenticated session but no elevated privileges. Given the high severity and the ease of exploitation, organizations should treat this as an immediate threat.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Appsmith to version 2.1 or later to apply the fix for
  • If upgrading is temporarily unavailable, disable or disable access to the Caddy admin API by blocking traffic to 0.0:2019 through firewall or container networking rules
  • Restrict SSRF or local request capabilities within the Appsmith deployment, ensuring only trusted services can resolve 0.0.0.0 addresses

Generated by OpenCVE AI on June 25, 2026 at 00:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Appsmith
Appsmith appsmith
Vendors & Products Appsmith
Appsmith appsmith
Type Values Removed Values Added
Description Appsmith is a platform to build admin panels, internal tools, and dashboards. Prior to 2.1, the bundled Caddy reverse-proxy's admin API — which has no authentication by default — is bound on 0.0.0.0:2019 inside the container. While this listener is not directly published to the host by docker-compose.yml, it is reachable from the Appsmith server process itself or a SSRF vulnerability. An authenticated low-privileged user can therefore drive the SSRF to issue POST /load (or any other admin-API call) against http://0.0.0.0:2019/, fully replacing the live Caddy configuration and taking over the reverse proxy. This vulnerability is fixed in 2.1.
Title Appsmith: Caddy admin API exposed without authentication
Weaknesses CWE-1188
CWE-749
References
Metrics cvssV3_1

{'score': 9.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}

Weaknesses
  • CWE-1188

    Initialization of a Resource with an Insecure Default

  • CWE-749

    Exposed Dangerous Method or Function

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jun 25, 2026, 3:11 PM
Reserved
Jun 16, 2026, 10:10 PM
Status
Analyzed
Published
Jun 24, 2026, 10:16 PM
Modified
Oct 25, 2026, 11:10 PM