CVE-2026-55454: CWE-749: Exposed Dangerous Method or Function in appsmithorg appsmith
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.
AI Analysis
Technical Summary
CVE-2026-55454 affects Appsmith versions before 2.1. The issue arises because the bundled Caddy reverse-proxy's admin API listens on 0.0.0.0:2019 inside the container without authentication. While docker-compose.yml does not expose this port externally, it remains accessible internally to the Appsmith server process or through SSRF vulnerabilities. An authenticated user with low privileges can leverage SSRF to send POST /load or other admin API calls to the Caddy admin endpoint, allowing full replacement of the live Caddy configuration and takeover of the reverse proxy. The vulnerability is resolved in Appsmith 2.1.
Potential Impact
Successful exploitation allows an authenticated low-privileged user to fully replace the live Caddy reverse proxy configuration, resulting in complete compromise of the reverse proxy component. This can lead to full control over traffic routing and potentially further compromise of the Appsmith environment. The CVSS v3.1 score is 9.9 (critical), indicating high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Appsmith to version 2.1 or later, where this vulnerability is fixed. Since the vulnerability is resolved in 2.1, applying this official fix is the recommended remediation. No additional mitigations are specified.
CVE-2026-55454: CWE-749: Exposed Dangerous Method or Function in appsmithorg appsmith
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.
CVSS v3.1
Score 9.9critical
Affected software
pkg:github/appsmithorg/appsmithRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-55454 affects Appsmith versions before 2.1. The issue arises because the bundled Caddy reverse-proxy's admin API listens on 0.0.0.0:2019 inside the container without authentication. While docker-compose.yml does not expose this port externally, it remains accessible internally to the Appsmith server process or through SSRF vulnerabilities. An authenticated user with low privileges can leverage SSRF to send POST /load or other admin API calls to the Caddy admin endpoint, allowing full replacement of the live Caddy configuration and takeover of the reverse proxy. The vulnerability is resolved in Appsmith 2.1.
Potential Impact
Successful exploitation allows an authenticated low-privileged user to fully replace the live Caddy reverse proxy configuration, resulting in complete compromise of the reverse proxy component. This can lead to full control over traffic routing and potentially further compromise of the Appsmith environment. The CVSS v3.1 score is 9.9 (critical), indicating high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
Upgrade Appsmith to version 2.1 or later, where this vulnerability is fixed. Since the vulnerability is resolved in 2.1, applying this official fix is the recommended remediation. No additional mitigations are specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T22:10:37.607Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c501e4853345fc1e45c57
Added to database: 06/24/2026, 21:46:06 UTC
Last enriched: 07/01/2026, 22:40:50 UTC
Last updated: 08/08/2026, 12:41:11 UTC
Views: 121
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.