Quick answers
- Is CVE-2026-55455 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55455 being exploited in the wild.
- How severe is CVE-2026-55455?
- Informational severity, with a CVSS score of 5.3, published 24 June 2026.
- Which products and versions are affected?
- Appsmith Community Edition <= 2.0; Appsmith Enterprise Edition <= 2.0.
- Is there a fix for CVE-2026-55455?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-55455 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-55455?
- Check whether you run Appsmith Community Edition or Appsmith Enterprise Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in Appsmith's WebClientUtils component. The outbound HTTP host filter uses an exact-match string denylist rather than comprehensive address-class validation (e.g., loopback, link-local, or any-local checks). Authenticated users can bypass these filters using alternative loopback representations like '0.0.0.0', '127.0.0.2', or '[::]'. This allows attackers to reach loopback-bound services inside the container, such as internal admin APIs. The vulnerability is fixed in version 2.1 by implementing proper IP address class resolution and validation.
Affected products
- Appsmith Appsmith Community Edition <= 2.0
- Appsmith Appsmith Enterprise Edition <= 2.0
Timeline
- 2026-06-12: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: CVE published to NVD