CVE-2026-55454·Docker vulnerability
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.
- Severity
- critical
- Software
- Docker
- Fixed in
- 2.1
- Published
- 2026-06-24
Affected versions
Until: 2.1
Fixed in: 2.1
How to fix this CVE
Upgrade Docker to version 2.1 or later to patch the unauthenticated Caddy reverse-proxy admin API exposure. This vulnerability allows authenticated users to leverage Server-Side Request Forgery (SSRF) to reconfigure the reverse proxy and intercept traffic. Immediately update your Docker installation and restart affected containers to apply the security fix.
sudo dnf upgrade -y docker-ceDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check Docker version: docker --version | grep -oP '\d+\.\d+' and confirm it is 2.1 or later
- Step 2: Verify Caddy admin API is not exposed: netstat -tlnp | grep 2019 or ss -tlnp | grep 2019 (should return no results if not running)
- Step 3: Check container logs for suspicious POST requests to /load endpoint: docker logs <container-name> | grep -i 'caddy\|/load\|2019'
- Step 4: Confirm the patch: docker inspect <image-id> | grep -i version and verify the image version is 2.1+
FAQ
What is CVE-2026-55454?
This vulnerability exposes Docker's bundled Caddy reverse-proxy admin API without authentication on port 2019. An authenticated attacker can abuse SSRF to remotely reconfigure the reverse proxy, allowing full interception and manipulation of application traffic.
Is CVE-2026-55454 being actively exploited?
No, this vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no public exploit code has been released. However, the attack method is straightforward for authenticated users with network access.
What versions of Docker are affected by CVE-2026-55454?
All versions of Docker prior to version 2.1 are affected. Version 2.1 and later include the security patch.
How do I check if my server is vulnerable to CVE-2026-55454?
Run 'docker --version' to check your installed version. If it is below 2.1, your installation is vulnerable. Additionally, test internal connectivity: 'curl -v http://127.0.0.1:2019/' from within a container; if port 2019 responds, the admin API is exposed.
Does Defensia detect CVE-2026-55454?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2026-55454 will appear in your dashboard with remediation steps.
Related Docker CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-55454. Free for 1 server.
Get started free