Skip to main content
VulnerabilityPublished

CVE-2026-55454: appsmithorg appsmith · Exposed Dangerous Method or Function

Affects appsmithorg appsmithSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 2.1 as a priority.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade appsmith and appsmithorg/appsmith to 2.1.

Affected software

ProductAffectedFixed in
appsmithorgappsmithAffected
  • <2.1
Fixed in
  • 2.1
GitHubappsmithorg/appsmithpkg:github/appsmithorg/appsmithOther threatsAffected
  • <2.1
Fixed in
  • 2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…