dbcve.org
AppsmithApplication

CVE-2026-55454

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Appsmith versions prior to 2.1, the bundled Caddy reverse-proxy's unauthenticated admin API listens on 0.0.0.0:2019 inside the container. An authenticated low-privileged user can leverage an SSRF vulnerability to issue POST requests to the Caddy admin API at http://0.0.0.0:2019/, allowing full replacement of the live Caddy configuration and takeover of the reverse proxy.

MitigationUpgrade to Appsmith version 2.1 or later. Additionally, audit for any existing SSRF vulnerabilities that could be chained with this attack vector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AppsmithApplication
Affected:< 2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Appsmith version
    Locate the version file or check the installation (common locations: ~/appsmith/VERSION or in the admin settings UI). Compare the version number to the affected range.
    Affected if The installed version is prior to 2.1 (e.g., 2.0.x, 1.x.x series)
  2. Verify Caddy admin API binding
    Inspect the Caddy configuration file (typically in the Appsmith container at /opt/caddy/Caddyfile or similar) or check the listening address. Look for the admin API bind directive.
    Affected if The Caddy admin API is configured to listen on 0.0.0.0:2019 rather than localhost only (127.0.0.1:2019)
  3. Confirm port 2019 accessibility
    From inside the Appsmith container, run 'netstat -tlnp | grep 2019' or 'ss -tlnp | grep 2019' to verify the binding address.
    Affected if Port 2019 is bound to 0.0.0.0 rather than 127.0.0.1
  4. Identify SSRF attack surface
    Review application endpoints that accept user-controlled URLs, particularly those used for webhooks, integrations, or resource fetching. Test if these endpoints can reach internal addresses like 127.0.0.1 or 0.0.0.0.
    Affected if Any endpoint allows fetching from or posting to internal URLs (127.0.0.1, 0.0.0.0, internal hostnames) without proper validation

You are affected if running Appsmith version prior to 2.1 AND the Caddy admin API is exposed on 0.0.0.0:2019 AND your application has an SSRF vulnerability that can reach the internal container network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1 or later
Fixed in 2.1
Interim mitigation

Upgrade to Appsmith version 2.1 or later. Additionally, audit for any existing SSRF vulnerabilities that could be chained with this attack vector.

Recommended fix High confidence

Appsmith 2.1 or later

  1. Upgrade Appsmith to version 2.1 or later to obtain the fixed Caddy configuration
  2. After upgrading, verify that the Caddy admin API is no longer exposed on 0.0.0.0:2019 or is properly authenticated
  3. Confirm the upgrade was successful by checking the Appsmith version in the admin settings
Caveat Review Appsmith 2.1 release notes for any breaking changes from pre-2.1 versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Appsmith Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55454 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data